Workflow for multi-environment management + promoting releases between environments
Open
area/pipeline
enhancement
pm
- Dominant language
- Go
- Stars
- 569
- Forks
- 364
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 136
Description
Developers may want different IaC for each environment (dev, test, prod).
- What is our guidance for managing that?
- How do we enable a developer to advance their app from one environment to another (e.g. dev -> prod)?
Note that using branches for management is sort of an anti-pattern/dated approach and there are developers who do not view this as an option (e.g. https://codefresh.io/blog/stop-using-branches-deploying-different-gitops-environments/)
Contributor guide
Assessment
This issue has not been assessed yet.