chore: Bicep Parameter validation email format change#2212
Merged
Conversation
Roopan-Microsoft
approved these changes
May 8, 2026
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, structured HTML email report for Bicep parameter validation results, and integrates it into the GitHub Actions workflow. The workflow now generates and sends visually improved email notifications with detailed validation results, replacing the previous plain-text approach. The main changes are grouped below:
Workflow and Notification Improvements:
.github/workflows/validate-bicep-params.yml) now generates an HTML report (email_body.html) using the validation script and attaches it as an artifact. The notification steps have been updated to send this HTML report as the email body instead of a plain-text summary. [1] [2] [3]Validation Script Enhancements:
generate_html_reportand supporting code toscripts/validate_bicep_params.pyto build a detailed, Outlook-compatible HTML report summarizing validation results, including error/warning counts and per-file breakdowns.--html-output,--accelerator-name, and--run-urlto support HTML report generation with contextual metadata.--html-outputargument is provided.Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information