You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
colleenXu
added
On CI
Related changes are deployed to CI server
On Test
Related changes are deployed to Test server
and removed
On CI
Related changes are deployed to CI server
labels
Jun 20, 2024
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: