Description:
Suggested this feature to be out-of-scope on #2965, will implement separately. Goal of this will be to enhance seed_db to be schema-aware and perhaps to build out a catalog of version::schema for future testing and development.
Acceptance Criteria:
[ ] Utility must be able to differentiate between versions of TDP
[ ] seed_db command must adapt certain fields to older versions
[ ] Testing Checklist has been run and all tests pass
[ ] README is updated, if necessary
Tasks:
[ ] Implement version/schema-tracking mechanism (we should be able to use django's migration table)
[ ] Tie above into seed_db command
[ ] Parameterize seed_db::validValues with version/schema notation to affect outcome
[ ] Run Testing Checklist and confirm all tests pass
Notes:
Update indicator validation was recently changed, that might be a good first MVP.
Supporting Documentation:
Open Questions:
What is priority and/or value-add of this in relation to beyond 4.0 API submissions?
Can this be tied into integration testing via cypress?
Description: Suggested this feature to be out-of-scope on #2965, will implement separately. Goal of this will be to enhance
seed_dbto be schema-aware and perhaps to build out a catalog of version::schema for future testing and development.Acceptance Criteria:
seed_dbcommand must adapt certain fields to older versionsTasks:
seed_dbcommandseed_db::validValueswith version/schema notation to affect outcomeNotes:
Supporting Documentation:
Open Questions: