add infrastructure for clearing repository and running seeds #5472
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.
This puts in place a series of classes that support generation of seed data.
Pattern
The pattern handles 3 scenarios. NOTE: all paths to files start from
app/utils
.data_maintenance.rb
and files underdata_destroyers
)required_data_seeder.rb
and files underrequired_data_seeders
)test_data_seeder.rb
and files undertest_data_seeders
)Benefits
Benefits of this approach:
To run:
NOTE: These examples show setting environment variables from the command line. They can be set in the regular way that an app sets environment variables. But since the running of seeds is generally not something you want to run all the time, it seems more like that setting the environment variables from the command line is a more common approach for seeds.
To list options without running anything...
To wipe data and generate required data...
To generate release data...
To run both...
Related Work
Issue #5351
PR #5056
@samvera/hyrax-code-reviewers