ci: Add Bicep parameter validation workflow and script#2149
Open
Harsh-Microsoft wants to merge 2 commits intoAzure-Samples:devfrom
Open
ci: Add Bicep parameter validation workflow and script#2149Harsh-Microsoft wants to merge 2 commits intoAzure-Samples:devfrom
Harsh-Microsoft wants to merge 2 commits intoAzure-Samples:devfrom
Conversation
…ification conditions
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 introduces a new GitHub Actions workflow for validating Bicep parameter files in the repository. The workflow is designed to run automatically on a schedule, on pull requests to main and dev branches, and can also be triggered manually. It checks the integrity of Bicep parameter mappings, uploads validation results, and sends email notifications to the team based on the outcome.
The most important changes are:
New CI/CD Workflow for Bicep Parameter Validation
.github/workflows/validate-bicep-params.ymlto automate validation of Bicep parameter files in theinfra/directory. The workflow runs on a schedule (weekly), on pull requests tomainanddev, and via manual triggers.scripts/validate_bicep_params.pyto perform strict validation, outputs results to summary and artifact, and fails the workflow if errors are detected.Notification and Reporting Enhancements
infra_results.json) and retained for 30 days for audit and troubleshooting purposes.Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information