chore: Bicep Parameter validation email format change#228
Merged
Roopan-Microsoft merged 7 commits intomicrosoft:devfrom May 8, 2026
Merged
chore: Bicep Parameter validation email format change#228Roopan-Microsoft merged 7 commits intomicrosoft:devfrom
Roopan-Microsoft merged 7 commits intomicrosoft:devfrom
Conversation
Roopan-Microsoft
approved these changes
May 7, 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 enhances the Bicep parameter validation workflow by introducing structured HTML email reporting, updating parameter naming for clarity and consistency, and improving the notification process. The main themes are improved reporting and parameter standardization.
Key changes:
1. Enhanced Reporting & Notifications
scripts/validate_bicep_params.py, including a newgenerate_html_reportfunction and CLI options for HTML output, accelerator name, and workflow run URL. This provides a more readable and professional notification format. [1] [2] [3].github/workflows/validate-bicep-params.yml) to generate and attach the HTML report, and to use its contents in notification emails instead of plain text. This change improves the clarity and presentation of validation results sent to the team. [1] [2] [3]2. Parameter Naming Consistency
infra/main.parameters.jsonandinfra/main.waf.parameters.json. For example, replacedcontainerRegistryEndpointwithcontainerRegistryHost, and grouped AI-related parameters under a consistentai*prefix. This improves maintainability and reduces confusion. [1] [2]3. Environment Variable Alignment
${AZURE_ENV_IMAGE_TAG}to${AZURE_ENV_IMAGETAG}and${AZURE_ENV_EXISTING_LOG_ANALYTICS_WORKSPACE_RID}to${AZURE_ENV_LOG_ANALYTICS_WORKSPACE_ID}for consistency across the deployment process. [1] [2]Let me know if you'd like a walkthrough of the new HTML report structure or more details on any of these changes!
Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information