Refactor: separate pipelines per environment into single deployment pipeline #52
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
Previously we had separate
dev.yaml
andproduction.yaml
pipelines. In part because I was paranoid about what code was going where and tried to get security via code, e.g. thisvars/global.yaml
.Actually this is convoluted. Instead, we will
CI --> Dev --> Production
staging visualization that many customers want.Instead of looking for which branch triggered the deployment, we can recognize from the circles, which environment was deployed. Note: in the current YAML,
main
andproduction
are separate triggers. So you will never get all 3 stages (e.g. circles) green in a single pipeline run.