-
-
Notifications
You must be signed in to change notification settings - Fork 65
feat: add --forceActions option to current #255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+94
−10
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
eaeeb60
Revert "Remove forceActions flag"
benjie 80224fc
Forcing actions shouldn't force migration to run
benjie 5c07d0a
Update README
benjie 955b135
Clarify docs, fix omission
benjie d808bde
Add tests that expected actions are called
benjie File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,9 +13,10 @@ export function makeCurrentMigrationRunner( | |
| options: { | ||
| once?: boolean; | ||
| shadow?: boolean; | ||
| forceActions?: boolean; | ||
| } = {}, | ||
| ): () => Promise<void> { | ||
| const { shadow = false } = options; | ||
| const { shadow = false, forceActions = false } = options; | ||
| async function run(): Promise<void> { | ||
| const currentLocation = await getCurrentMigrationLocation(parsedSettings); | ||
| const body = await readCurrentMigration(parsedSettings, currentLocation); | ||
|
|
@@ -74,14 +75,17 @@ export function makeCurrentMigrationRunner( | |
| migrationsAreEquivalent = | ||
| currentBodyMinified === previousBodyMinified; | ||
|
|
||
| // 4: if different | ||
| if (!migrationsAreEquivalent) { | ||
| // 3a: Run actions if the migrations are different OR if forced. | ||
| if (forceActions || !migrationsAreEquivalent) { | ||
| await executeActions( | ||
| parsedSettings, | ||
| shadow, | ||
| parsedSettings.beforeCurrent, | ||
| ); | ||
| } | ||
|
|
||
| // 4: if different | ||
| if (!migrationsAreEquivalent) { | ||
| // 4a: invert previous current; on success delete from graphile_migrate.current; on failure rollback and abort | ||
| if (previousBody) { | ||
| await reverseMigration(lockingPgClient, previousBody); | ||
|
|
@@ -135,7 +139,7 @@ export function makeCurrentMigrationRunner( | |
| ); | ||
| const interval = process.hrtime(start); | ||
| const duration = interval[0] * 1e3 + interval[1] * 1e-6; | ||
| if (!migrationsAreEquivalent) { | ||
| if (forceActions || !migrationsAreEquivalent) { | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @maxkorp unless I messed up all the merges, I think you omitted this change previously? |
||
| await executeActions( | ||
| parsedSettings, | ||
| shadow, | ||
|
|
||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maxkorp This is different to your previous logic - the actions are now ran independently of the database changes themselves being implemented. Is this desired? I think it effectively makes little difference since we're in a transaction so the changes aren't visible anyway...