biothings / biothings_explorer

TRAPI service for BioThings Explorer
https://explorer.biothings.io
Apache License 2.0
10 stars 11 forks source link

Remove temporary config changes (rolling deployment chore) #811

Open colleenXu opened 7 months ago

colleenXu commented 7 months ago

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:

We can't remove SmartAPI yaml branches used for the temporary overrides until the overrides have been removed from all instances.

colleenXu commented 7 months ago

For the current Translator Sprint (2/Octopus):

colleenXu commented 5 months ago

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 https://github.com/biothings/bte-server/pull/30:

EDIT: Done 7/31. 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): https://github.com/NCATS-Tangerine/translator-api-registry/pull/153

tokebe commented 4 months ago

Eel changes deployed to Prod, resetting tracking label.

colleenXu commented 4 weeks ago

@tokebe

If we do any hot-fixes/ CI -> Test deployments for this last sprint / end of phase, can we include https://github.com/biothings/bte-server/pull/51?

It's fine to do because I've already merged the PFOCR yaml update to master. So these changes are live on all instances already. See more notes in https://github.com/biothings/biothings_explorer/issues/882#issuecomment-2445867781


Documenting our decision on the other overrides...

We agreed to keep the overrides for "removing clinical trial operations" for this phase: