feat: Added Deployment v2 pipeline#521
Open
Rafi-Microsoft wants to merge 38 commits intomicrosoft:mainfrom
Open
feat: Added Deployment v2 pipeline#521Rafi-Microsoft wants to merge 38 commits intomicrosoft:mainfrom
Rafi-Microsoft wants to merge 38 commits intomicrosoft:mainfrom
Conversation
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 introduces a new, modular GitHub Actions workflow system for deploying, testing, and cleaning up Azure-based resources, with a focus on orchestrating deployments and supporting Linux-based infrastructure. The changes add several reusable workflow files that can be composed together, improving maintainability and flexibility for different deployment scenarios.
Key changes include:
New Orchestrator and Workflow Structure
Added a central orchestrator workflow (
deploy-orchestrator.yml) that coordinates the deployment, end-to-end testing, notification, and cleanup jobs, with support for configurable inputs such as Azure region, resource group, WAF/EXP toggles, and test suite selection. This workflow delegates actual work to job-specific workflow files for modularity.Introduced a new top-level workflow (
deploy-windows.yml) designed to trigger deployments for Linux-based infrastructure on specific branches, schedules, or manual dispatch. It collects user inputs and invokes the orchestrator workflow.Modular Job Workflows
Added a reusable deployment job for Linux(
job-deploy-windows.yml) that handles all deployment steps, including parameter configuration, Azure/Kubernetes/Helm setup, resource provisioning, health checks, post-deployment scripting, and job summary reporting. Outputs the deployed web app URL for downstream jobs.Added a cleanup job workflow (
job-cleanup-deployment.yml) that logs into Azure, deletes the specified resource group asynchronously, handles logout, and generates a cleanup summary, supporting robust teardown of test environments.These changes lay the groundwork for a more maintainable, flexible, and observable CI/CD pipeline for Azure deployments.
Most important changes:
Workflow Orchestration and Structure
deploy-orchestrator.ymlto coordinate deployment, testing, notification, and cleanup jobs, using modular workflow calls and supporting extensive input customization.deploy-windows.ymlas a trigger workflow for Linux-based deployments, supporting branch, schedule, and manual triggers, and passing parameters to the orchestrator.Modular Job Definitions
job-deploy-windows.ymlto encapsulate all deployment logic for Linux environments, including environment setup, Azure/Kubernetes/Helm configuration, deployment execution, health checks, post-deployment steps, and summary reporting.job-cleanup-deployment.ymlfor resource group cleanup, including Azure authentication, asynchronous deletion, logout, and job summary generation.Parameterization and Reporting
Does this introduce a breaking change?