Skip to content

Conversation

@Dhruvkumar-Microsoft
Copy link
Contributor

Purpose

This pull request focuses on standardizing Azure resource naming, environment variable usage, and deployment parameters throughout the codebase. It also improves post-deployment feedback and updates documentation for clarity. The changes are primarily in CI/CD workflow files, infrastructure templates, and documentation.

CI/CD Workflow Improvements and Environment Variable Updates:

  • Updated all workflow files (deploy.yml, test-automation.yml, etc.) to use AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, and AZURE_SUBSCRIPTION_ID instead of the previous maintenance-specific variables, ensuring consistency and simplifying secret management. [1] [2] [3] [4]
  • Added AZURE_DEV_COLLECT_TELEMETRY variable to the Azure Dev workflow for improved telemetry control.

Infrastructure Template and Parameter Standardization:

  • Changed deployment parameters from environmentName to solutionName and from aiDeploymentsLocation to aiServiceLocation in both main and WAF parameter files, aligning with updated naming conventions. [1] [2] [3] [4] [5]
  • Enhanced WAF parameter file (renamed to main.waf.parameters.json) to include new fields for monitoring, scalability, and VM credentials.

Infrastructure Module Improvements:

  • Updated resource module names in Bicep files to use the take function for length-limited, standardized naming, improving resource traceability and compliance. [1] [2] [3]
  • Improved diagnostic settings logic for Key Vault to handle empty workspace IDs more robustly.

Post-Deployment Feedback Enhancement:

  • Enhanced post-deployment hooks in azure.yaml to display detailed web and API app information, including endpoints and Azure portal links, for both POSIX and Windows environments.

Documentation Updates:

  • Updated authentication setup instructions in ConfigureAppAuthentication.md to reflect new resource naming conventions (ca-<randomname>-web and ca-<randomname>-api), ensuring documentation matches deployment outputs. [1] [2] [3] [4] [5] [6]

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

Vemarthula-Microsoft and others added 24 commits October 13, 2025 17:38
feat: Network module changes and fix
fix: Optimize Network Module Deployment & Apply WAF Standardization fixes
fix: Adding condition to keyvault diagnostic settings
chore: Add AZURE_DEV_COLLECT_TELEMETRY in azure-dev.yml file
@Roopan-Microsoft Roopan-Microsoft merged commit f5427bc into main Oct 20, 2025
9 checks passed
Prajwal-Microsoft added a commit that referenced this pull request Oct 21, 2025
Merge pull request #292 from microsoft/dev
@github-actions
Copy link

🎉 This PR is included in version 1.10.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants