Heroku rollbacks create a new version of the app but use the commit hash from the targeted version.
eg:
Release: v1, hash: 1
Release: v2, hash: 2
rollback v1
Release: v3, hash: 1
This means that if we want to rollback to v2 again - we need the up scripts from hash 2. But these have been removed as part of the mongo-migrator rollback.
The workaround is to push a new version that performs a migrate and the scripts are added.
The question is - how typical is it to rollback twice?
Heroku rollbacks create a new version of the app but use the commit hash from the targeted version.
eg:
Release: v1, hash: 1
Release: v2, hash: 2
This means that if we want to rollback to v2 again - we need the up scripts from hash 2. But these have been removed as part of the mongo-migrator rollback.
The workaround is to push a new version that performs a migrate and the scripts are added.
The question is - how typical is it to rollback twice?