Closed jwenz723 closed 3 years ago
This is a rather broad topic depending on many factors.
In simple terms and in general, I recommend splitting modules away from this repository and have them in their own pipeline.
Once a new module version is released, this repository is updated with PR to acme-staging
, which is deployed to staging after merge.
GitHub's PR is not a replacement to manual approval's, but Atlantis and other forms of GitOps can act as approval step in your pipeline.
I highly recommend reading http://infrastructure-as-code.com/ and Kief's books where he covers these topics in much more details.
Do you have any suggestions for what a work flow would look like for the developers interacting with a repository following the same structure as this repository?
Things that would be interesting to understand your opinion on: