Allow user to turn off backfill corrections file generation #1810
Conversation
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
nmdefries
changed the title
Contributor
Author
Contributor
|
It looks good to me, and should be pretty useful for local runs |
Contributor
Author
|
@krivard This is ready to merge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Don't run backfill corrections file generation and don't require backfill-related params (dir, etc) if user asks to turn off file generation via params flag. By default, if flag is not set, backfill files are generated. Local params template sets flag to
false(backfill files not generated), and production params template sets flag totrue.Changelog
changehc,quidel_covidtest, andclaims_hospbackfill file generation to be enclosed inifstatementFixes
Closes #1797