docs: document ALLOW_MISSING_MIGRATIONS env var#640
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
🤖 Documentation Bot✅ All checks passed! No issues found. |
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Documents the new
ALLOW_MISSING_MIGRATIONSenvironment variable, which disables Knex's migration list validation so an older Lightdash version can start against a newer database during rollbacks.Changes
ALLOW_MISSING_MIGRATIONSrow to the environment variables reference, alongside the otherPG*database variables.Context
Upstream PR introduces a configurable migration list validation. When rolling back code while the database stays on a newer schema, the health check would previously fail because migrations existed in
knex_migrationswithout matching files on disk. SettingALLOW_MISSING_MIGRATIONS=truesuppresses only the "DB ahead of code" check; pending migrations are still detected.