chore: dev to main merge

[Saswato-Microsoft]

Purpose

This pull request introduces several workflow and script improvements to enhance Azure deployment automation, template validation, and version compatibility. The main changes include splitting template validation into a dedicated workflow, refining the deployment workflow, improving tag handling logic in provisioning scripts, and enforcing required tool versions.

Workflow and automation improvements:

• Added a new .github/workflows/azd-template-validation.yml workflow to validate Azure Developer (AZD) templates on pushes to main, on schedule, and on manual dispatch. This separates template validation from deployment and improves CI clarity.
• Refactored .github/workflows/azure-dev.yml to focus solely on deployment, removing template validation steps and updating environment setup, Azure login, and deployment logic for better reliability and maintainability.
• Updated .github/workflows/daga-automation-oidc.yml to trigger only when changes are made to relevant infrastructure and script files, reducing unnecessary workflow runs.

Provisioning and tagging logic improvements:

• Overhauled tag handling in hooks/postprovision.ps1 by removing the Add-TagSource function and replacing it with a clear priority chain: CLI -Tags > DAGA_POSTPROVISION_TAGS environment variable > Bicep dagaTags parameter > fallback. This ensures consistent and predictable tag application. [1] [2]
• Enhanced Bicep parameter parsing in hooks/postprovision.ps1 to support newer Bicep CLI output formats, improving compatibility with recent tool versions.

Version enforcement:

• Added a requiredVersions section to azure.yaml to enforce minimum versions of azd and bicep, and to explicitly exclude a problematic azd version, preventing deployment failures due to incompatible tooling.

Does this introduce a breaking change?

• Yes
• No

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information

[Copilot]

Pull request overview

This PR refactors CI/CD automation for the Azure Developer CLI (azd) template by splitting template validation into a dedicated workflow, tightening workflow triggers, improving post-provision tag resolution, and enforcing minimum tool versions via azure.yaml.

Changes:

• Added a dedicated AZD template validation workflow and refocused the existing workflow to deployment-only.
• Updated post-provision hook logic to use a deterministic tag priority chain and improved parsing of newer Bicep CLI build-params output.
• Added requiredVersions in azure.yaml and constrained the OIDC automation workflow to run only on relevant path changes.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
hooks/postprovision.ps1	Improves tag selection precedence and updates Bicep parameter parsing to handle newer CLI output shapes.
azure.yaml	Enforces minimum azd/bicep versions (and excludes a known-bad azd version).
.github/workflows/daga-automation-oidc.yml	Limits push-triggered runs to infra/script/spec changes to reduce unnecessary executions.
.github/workflows/azure-dev.yml	Refactors workflow to run azd-based provisioning/deploy on main pushes and manual dispatch.
.github/workflows/azd-template-validation.yml	Introduces a separate validation workflow (push/schedule/manual) using template-validation action.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

🎉 This PR is included in version 1.0.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀