233: Hookup A&R to Data Register. #267
Conversation
marklise
requested review from
danieltruong,
meredithom,
cameronpettit and
Christopher-walsh22
There was a problem hiding this comment.
I would point DEV, TEST and PROD all to the prod instance of Data Register - its an entirely different project, we should be able to assume it's complete and functional for the contexts of the DEV/TEST A&R environments.
Obviously though we don't have a vanity prod URL for Data Register - I would say you can merge this but the ticket should be moved to blocked.
|
To add to my above comment - consider the the future case where A&R and the Data Register are potentially handed off to two different maintenance teams. I'm not sure it would be best to have the testing envs of one project be reliant on the testing envs of another when a future maintenance team may not have access to both. |
|
Kudos, SonarCloud Quality Gate passed!
|
Fixes #233
Two new environment variables have been setup - their default configurations are setup in the parameter store.
There is a cronjob that is setup to run every midnight. The first run of the job will update ALL names in the A&R table to whatever they are set to in the data register. On subsequent runs, the code will only update the records in question that have changed from the data register.
A new index against the A&R table is setup (orcs-index) which allows the code to efficiently query all records via orcs.
TODO: Update the parameter store variables with TEST and PROD data that point to the appropriate API endpoint for DR TEST and PROD.