Skip to content

chore: Bicep Parameter validation email format change#228

Merged
Roopan-Microsoft merged 7 commits intomicrosoft:devfrom
NirajC-Microsoft:dev
May 8, 2026
Merged

chore: Bicep Parameter validation email format change#228
Roopan-Microsoft merged 7 commits intomicrosoft:devfrom
NirajC-Microsoft:dev

Conversation

@NirajC-Microsoft
Copy link
Copy Markdown
Contributor

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

  • Added HTML email report generation to scripts/validate_bicep_params.py, including a new generate_html_report function and CLI options for HTML output, accelerator name, and workflow run URL. This provides a more readable and professional notification format. [1] [2] [3]
  • Updated the GitHub Actions workflow (.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

  • Standardized and clarified parameter names in infra/main.parameters.json and infra/main.waf.parameters.json. For example, replaced containerRegistryEndpoint with containerRegistryHost, and grouped AI-related parameters under a consistent ai* prefix. This improves maintainability and reduces confusion. [1] [2]

3. Environment Variable Alignment

  • Updated parameter value substitutions to match new environment variable names, such as changing ${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?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • ...

Other Information

This comment was marked as resolved.

@Roopan-Microsoft Roopan-Microsoft merged commit ebd74d3 into microsoft:dev May 8, 2026
25 of 28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants