ci: workflow to automate the validation of Bicep parameter files#895
Open
Harsh-Microsoft wants to merge 3 commits intodev-v4from
Open
ci: workflow to automate the validation of Bicep parameter files#895Harsh-Microsoft wants to merge 3 commits intodev-v4from
Harsh-Microsoft wants to merge 3 commits intodev-v4from
Conversation
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 to automate the validation of Bicep parameter files in the repository. The workflow runs on a schedule, on pull requests affecting infrastructure files, and can be triggered manually. It validates parameter mappings, summarizes the results, uploads artifacts, and sends email notifications based on the outcome.
The most important changes are:
CI/CD Automation:
.github/workflows/validate-bicep-params.ymlto automatically validate Bicep parameter files (.bicepand.parameters.json) in theinfra/directory on a schedule, on relevant pull requests, and via manual dispatch.Validation and Reporting:
validate_bicep_params.pyscript, which outputs results to both a summary and an artifact (infra_results.json).Notification System:
Fail-fast Mechanism:
Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information