Merged
Conversation
fix: merging dev to main
Added note for azd version 1.23.9 regarding preflight command.
docs: Update Deployment Guide with azd version note
ci: refactor notification email templates
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the GitHub Actions deployment orchestration and notification reusable workflow to explicitly track/report cleanup status in notifications, along with a small deployment guide update for azd preflight behavior.
Changes:
- Adds a dedicated
cleanup-deploymentjob to the deployment orchestrator and wires its result into the notification job. - Enhances the notification workflow to compute cleanup status + configuration label and include a stage summary table in email bodies/subjects.
- Adds an
azdconfiguration note to the deployment guide.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| docs/DeploymentGuide.md | Adds a note/command for disabling azd preflight. |
| .github/workflows/job-send-notification.yml | Adds cleanup_result input, cleanup/config label computation, and richer email templates. |
| .github/workflows/deploy-orchestrator.yml | Introduces cleanup-deployment job and passes its job result into the notification workflow. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Roopan-Microsoft
approved these changes
Mar 26, 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 deployment workflow and notification system by introducing explicit tracking and reporting of the cleanup job's status, improving the clarity of email notifications, and simplifying input validation for the notification job. The changes ensure that the cleanup phase is properly handled and its outcome is reflected in notifications, while also making status summaries and configuration details more visible and user-friendly.
Key changes include:
Workflow Orchestration and Cleanup Handling
cleanup-deploymentjob to.github/workflows/deploy-orchestrator.yml, which runs after deployment and e2e tests, and passes its result to the notification job for reporting. The notification job now depends on the cleanup job.Notification Job Improvements
job-send-notification.yml) now accepts acleanup_resultinput, determines a human-readable cleanup status, and generates a configuration label (e.g., "WAF + EXP") for use in notifications. [1] [2]Input Validation Simplification
Input Defaults and Requirements
e2e_test_resultandcleanup_resultinputs optional with sensible defaults, improving robustness when these values are not set. [1] [2]These changes collectively make the deployment process more robust and transparent, especially in reporting the state of resource cleanup and overall pipeline status.
Workflow Orchestration and Cleanup Handling
cleanup-deploymentjob to the orchestrator workflow, ensuring cleanup runs after deployment and e2e tests, and feeds its result into the notification process.Notification Job Improvements
Input Validation and Defaults
e2e_test_resultandcleanup_resultinputs optional with defaults, increasing resilience to missing data. [1] [2]Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information