Remove temporary config changes (rolling deployment chore)
colleenXu opened this issue · comments
Often, we use temporary overrides or other config adjustments to handle the staggered deployment of features (Dev -> CI -> Test -> Prod). We direct BTE to use updated/changed SmartAPI yamls.
Once the features are deployed to Prod (on all instances), we have a chore to remove them:
- make the changes into the default
- merge the SmartAPI yaml changes to the master branch (registered yamls)
- for TRAPI updates, update the registered yaml to latest TRAPI + all server urls. Then delete the temporary registrations used in the exclusions
- remove the temporary overrides or other config adjustments
- put into the next deployment cycle
We can't remove SmartAPI yaml branches used for the temporary overrides until the overrides have been removed from all instances.
For the current Translator Sprint (2/Octopus):
- We have SmartAPI overrides for biolink-4/treats-refactor and source_record_urls
- We have SmartAPI exclusions for the temporary TRAPI 1.5 registrations
Update: sprint 2/Octopus has deployed to Prod.
We've decided to add this chore to Eel the patch we're doing to Octopus with this PR biothings/bte-server#30:
- removing the SmartAPI exclusions for the temporary TRAPI 1.5 registrations. Those temporary registrations have already been deleted.
- removing SmartAPI overrides for treats-refactor/biolink-4. Can use the registered yamls, which have been updated (Service-Provider-only, text-mining targeted)
- removing SmartAPI overrides for the new
source_record_urlsfeature- Registered yamls for BioThings BindingDB and MyGene have been updated
- DIDN'T UPDATE BioThings PFOCR YET. We need to wait until Eel
the Octopus patchis released to all instances because it has code for handling the multiple urls in the PFOCR situation
Once the patch is deployed on all instances, then I can merge this PR to update BioThings PFOCR's registered yaml (which all instances will be using): NCATS-Tangerine/translator-api-registry#153