chore: dev to main merge

[Ragini-Microsoft]

Purpose

This pull request updates several GitHub Actions workflow files to standardize environment variable names, improve parameter validation, and refine workflow triggers. The main focus is on renaming variables (especially use case and resource IDs), updating input/output mappings, and tightening workflow execution to relevant file changes. These changes enhance consistency, maintainability, and reduce the risk of misconfiguration across deployment workflows.

Variable Renaming and Standardization

• Replaced AZURE_ENV_USE_CASE with USE_CASE across all workflows and their input/output mappings to unify naming conventions. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]
• Renamed resource ID variables for clarity and accuracy, including AZURE_ENV_LOG_ANALYTICS_WORKSPACE_ID → AZURE_ENV_EXISTING_LOG_ANALYTICS_WORKSPACE_RID and AZURE_EXISTING_AI_PROJECT_RESOURCE_ID → AZURE_EXISTING_AIPROJECT_RESOURCE_ID, updating all related validation, input, and output logic. [1] [2] [3] [4] [5] [6] [7] [8]

Workflow Trigger and Path Improvements

• Added path filters to workflow triggers so that deployments only run when relevant files or directories change, reducing unnecessary workflow executions. [1] [2] [3] [4]

Job and Step Adjustments

• Updated environment variable usage in deployment steps and azd env set commands to reflect the new standardized names and improve clarity (e.g., AZURE_ENV_AI_SERVICE_LOCATION, AZURE_ENV_GPT_MODEL_CAPACITY, AZURE_ENV_IMAGE_TAG). [1] [2]

Workflow Logic and Notification Handling

• Improved the notification job in orchestrator workflows to depend on cleanup and deployment jobs, ensuring notifications reflect the final deployment state.

Validation Logic Updates

• Updated all validation logic and error messaging to use the new variable names and ensure only allowed values are accepted for use case and resource ID parameters. [1] [2]

These changes collectively improve the reliability and maintainability of the deployment workflows by enforcing consistent variable naming, better input validation, and more targeted workflow execution.

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.