refactor(env-vars): check env vars in production for migration #7649
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#5932
Refactors migration to enforce setting environment variables in production. Doesn't use envalid to keep things simple.
NOTE!: Also adds a
set -e
torun-migrations.sh
to fail the whole script if any of the commands fails. I thought this is necessary for example in the case of reindexing search, if the Mongo migrations fail, the ElasticSearch gets bad data also.