chore: dev to main - Refactor Azure workflows and add Bicep parameter validation#863
Merged
Conversation
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…tification conditions
…edge-Mining-Solution-Accelerator into psl-ckm-uirefactoring
Added note about SFI issues during deployment.
Removed duplicate note about SFI issues and ensured clarity in deployment instructions.
Added a note regarding SFI issues during deployment and WAF support.
ci: Refactor azure-dev and azd-template-validation workflows
…edge-Mining-Solution-Accelerator into psl-ckm-uirefactoring
refactor: Reafctor CKM UI
docs: Added content in Readme and deploymentguide for SFI issue
revert: "refactor: Reafctor CKM UI"
Roopan-Microsoft
approved these changes
Apr 13, 2026
Contributor
|
🎉 This PR is included in version 3.21.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
github-actions Bot
pushed a commit
that referenced
this pull request
Apr 15, 2026
chore: dev to main - Refactor Azure workflows and add Bicep parameter validation
github-actions Bot
pushed a commit
that referenced
this pull request
Apr 15, 2026
chore: dev to main - Refactor Azure workflows and add Bicep parameter validation
github-actions Bot
pushed a commit
that referenced
this pull request
Apr 17, 2026
chore: dev to main - Refactor Azure workflows and add Bicep parameter validation
github-actions Bot
pushed a commit
that referenced
this pull request
Apr 17, 2026
chore: dev to main - Refactor Azure workflows and add Bicep parameter validation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request refactors and enhances the project's GitHub Actions workflows for Azure deployments and validation. The main changes include the addition of a dedicated workflow for validating Bicep parameters, the consolidation and modernization of Azure deployment and template validation workflows, and the introduction of stricter tooling version requirements. These updates improve automation, reliability, and maintainability of the CI/CD pipeline.
CI/CD Workflow Improvements
validate-bicep-params.yml, to automatically validate Bicep parameter files on a schedule and on pull requests, including notification steps for failures or successes.azd-template-validation.ymlworkflow to regularly validate Azure Developer (AZD) templates, replacing the olderazure-dev-validation.ymlworkflow. The new workflow supports scheduled runs and uses environment variables for flexible validation. [1] [2]azure-dev.ymlto use updated action versions, improved environment variable handling, and a more robust deployment process with environment selection and provisioning steps.Tooling and Version Requirements
azure.yamlto require Bicep CLI version 0.33.0 or higher, ensuring compatibility and consistency for infrastructure-as-code deployments.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation