chore: Add AZD Template Validation Workflow (Scheduled & On-Demand) and Refactor Azure Deployment Pipeline for RTI#67
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s GitHub Actions workflows to shift Azure deployment and AZD template validation toward manual/scheduled execution, reduce duplicated environment variable configuration, and improve generated environment name uniqueness to reduce collision risk.
Changes:
- Removed automatic
pushtriggers for Azure deployment and template validation workflows; added a scheduled cron trigger for template validation. - Centralized several shared template-validation-related environment variables at the workflow level.
- Updated environment name generation to include UTC
HHMMfor increased uniqueness.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
.github/workflows/azure-dev.yml |
Removes push triggers and updates environment name generation to include HHMM; adds shared template-validation env vars at workflow scope. |
.github/workflows/azd-ai-template-validation.yml |
Removes push triggers, adds weekly schedule, lifts common env vars to workflow scope, and updates validation environment naming to include time-based uniqueness. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Prajwal-Microsoft
approved these changes
Apr 8, 2026
|
🎉 This PR is included in version 1.3.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
This pull request updates the GitHub Actions workflows for Azure deployments and template validation. The main changes improve environment variable management, enhance environment name uniqueness, and adjust workflow triggers to streamline CI/CD processes.
Workflow trigger and scheduling changes:
azd-ai-template-validation.ymlandazure-dev.ymlworkflows are no longer triggered automatically on pushes tomainordevbranches; instead, they can be run manually or on a scheduled basis (every Thursday at 1:30 AM UTC for validation). [1] [2]Environment variable management:
TEMPLATE_USE_DEV_CONTAINER,TEMPLATE_VALIDATE_AZD,TEMPLATE_VALIDATE_TESTS, andAZURE_DEV_COLLECT_TELEMETRY) are now set globally at the workflow level, reducing duplication and ensuring consistency across jobs. [1] [2]Environment name generation improvements:
HHMM) in addition to a timestamp, making the names more unique and less likely to collide. This change affects both the validation and deployment workflows. [1] [2]Job environment variable usage:
envcontext instead of being set per job, and the environment name now incorporates the newHHMMcomponent.These changes should make the workflows more robust, easier to maintain, and better suited for scheduled and manual runs.## Purpose
Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information