feat: track seeded files in migration table #2728
Merged
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.
What kind of change does this PR introduce?
feature
What is the new behavior?
Track seed files in a history table.
path
resolves to local seed file and is also they primary keyhash
is the sha256 checksum of the seed fileWhen loading seed files, we check the history table for path and hash match. Any unmatched files will be seeded next.
If file path exists in history but checksum doesn't match, the seed file will be marked dirty. Dirty files are not seeded, only their hash column will be updated.
If both path and hash match, the seed file is skipped, as it has been applied before.
Additional context
Also prompts before creating custom roles.