A release process certifies a software change before distributing it to consumers. For a module update, test the change away from development and production workloads, then publish only when the tests pass. section 5.3
A practical module release follows these steps:
- Update the module and push the change to version control. section 5.3
- Ask a consumer team to test the module in a separate environment. section 5.3
- Tag the tested change, update documentation, and distribute it through a package manager, artifact repository, or storage bucket. section 5.3
Database module version 2.0.0
After adding secret-manager password storage, the infrastructure team asks the Fruits team to test the database module. Once confirmed, the team tags version 2.0.0 and updates the secrets-manager documentation. section 5.3
Figure 5.11 When you make module updates, ensure that you include a testing stage before releasing the module and updating its documentation.
Use the release flow as a checklist: module updates pass through testing before release and documentation updates. section 5.3
