add migrations to create tax household enrollments for missing reinstated enrollments #4910
+796
−0
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.
PR Checklist
Please check if your PR fulfills the following requirements:
let
helpers andbefore
blocks..html_safe
.PR Type
What kind of change does this PR introduce?:
What is the ticket # detailing the issue?
Ticket: https://www.pivotaltracker.com/story/show/188604585
A brief description of the changes:
Current behavior: Currently, Devops is manually upload a script file to server and running the script to generate tax household enrollments for missing enrollments
New behavior: Create a migration script to generate tax household enrollments for missing enrollments
Script 1:
Create Tax Household Enrollments for Missing Reinstated Enrollments
Command:
CLIENT=me bundle exec rails runner script/tax_household_enrollments/create_for_reinstated_enrollments.rb 2024
Output:
Generates a CSV file named
reinstated_enrollments_with_thh_enrs_creation_report.csv
Script 2:
Create Tax Household Enrollments for Specific Enrollment HBX IDs
Command:
CLIENT=me bundle exec rails runner script/tax_household_enrollments/create.rb "12345,67890,11223"
Output:
Generates a CSV file named
update_missing_slcsp_info_for_aptc_enrs_report_*.csv
Feature Flag
For all new feature development, a feature flag is required to control the exposure of the feature to our end users. A feature flag needs a corresponding environment variable to initialize the state of the flag. Please share the name of the environment variable below that would enable/disable the feature and indicate which client(s) it applies to.
Variable name:
Additional Context
Include any additional context that may be relevant to the peer review process.