2.5.1 Multi-Environment Strategy
We have so far created one identity account and two operational accounts viz. prod and dev where we'll deploy all the AWS resources. We need this multi-environment strategy so that we can verify our changes in the dev environment before pushing into the prod. This shall follow a specific pattern as described below
- Developer makes changes in the code for dev account.
- Creates a dev branch and pushes changes in the dev branch.
- Dev branch has details of only dev environment which then provisions the dev infrastructure
- Once dev infra changes are verified, a PR is raised.
- PR is verified and merged.
- Upon merge changes are pushed to main branch which is tied to Prod environment which then goes live.