chore: fixed security vulnerability #636
Open
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 deployment and cleanup workflow for both Linux and Windows environments, enhancing automation, flexibility, and maintainability for Azure resource management and testing. It adds orchestrator and job workflows to centralize deployment logic, supports configurable options for resource cleanup and end-to-end testing, and updates code ownership.
Workflow orchestration and modularization:
deploy-orchestrator.ymlto coordinate Docker build, deployment, testing, notification, and cleanup jobs, enabling reusable and maintainable workflow steps for deployments.job-cleanup-deployment.ymlto handle resource group cleanup with optimized Azure CLI commands and job summary reporting, improving resource management automation.Deployment pipeline improvements:
deploy-linux.yml) and Windows (deploy-windows.yml), supporting flexible inputs for Azure location, resource group, WAF, Docker image build, cleanup, and test suite selection. These workflows invoke the orchestrator for streamlined execution.Ownership and maintainability:
.github/CODEOWNERSto add@dgp10801as a default owner, ensuring proper code stewardship.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information