-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove temporary config changes (rolling deployment chore) #811
Comments
For the current Translator Sprint (2/Octopus):
|
Update: sprint 2/Octopus has deployed to Prod. We've decided to add this chore to Eel
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): NCATS-Tangerine/translator-api-registry#153 |
Eel changes deployed to Prod, resetting tracking label. |
If we do any hot-fixes/ CI -> Test deployments for this last sprint / end of phase, can we include biothings/bte-server#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 #882 (comment) Documenting our decision on the other overrides... We agreed to keep the overrides for "removing clinical trial operations" for this phase:
|
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.
The text was updated successfully, but these errors were encountered: