-
Notifications
You must be signed in to change notification settings - Fork 0
Release process: ror api
Liz Krznarich edited this page Mar 30, 2022
·
1 revision
Production ror-api Docker images are tagged with the release version, so it's possible to revert to a previous release by manually triggering a Terraform run that pulls a Docker image with a previous release tag.
- In https://github.com/ror-community/new-deployment/blob/master/ror/services/api/_ror-api.auto.tfvars, revert
sha
andversion
to the values that correspond to a previous release - Commit and push the changes to new-deployment/master
- Merge to master triggers a Terraform run that deploys a new container to ECS, using the Docker image corresponding to the release tag per https://github.com/ror-community/new-deployment/blob/d730bd9af44f93a3c28d0b5adb47b6ec6f30be0b/ror/services/api/main.tf
- In Github, revert the PR merge to ror-api/master
- In Github delete the published release (note that this does not delete the release tag)
- From your local machine, delete the release tag manually
git push --delete origin [tag]
Dev and staging ror-api Docker images are NOT tagged with a release version; they are tagged as "dev" and "staging" and are replaced on each deployment. As a result, it's only possible to revert to a previous version by making code changes and merging them to trigger a new deployment.