Feat/cd separate destroy workflows #19
Merged
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.
Summary
This PR introduces two independent GitHub Actions destruction workflows for TEST and STAGE while preserving the existing combined TEST/STAGE and dedicated PROD destruction workflows.
The change provides more granular control over infrastructure cleanup without modifying previously tested workflows.
Changes
Independent Destruction Workflows
.github/workflows/destroy-test.ymlfor TEST-only destruction..github/workflows/destroy-stage.ymlfor STAGE-only destruction.main.infrastructure-deploymentconcurrency group.Existing Workflows
destroy.ymlfor combined TEST and STAGE destruction.destroy-prod.ymlfor independently authorized PROD destruction.Documentation
README.mdto describe the destruction architecture, workflow responsibilities, and infrastructure lifecycle.Destruction Architecture
destroy-test.ymldestroy-stage.ymldestroy.ymldestroy-prod.ymlValidation