Change flow

This document covers various options for how changes can flow through a software infrastructure like the Global App.

In Global App, changes flow from QA to parallel staging environments for each region and then to production from there.

But this is just one of many possible flow choices. Another option could be to have one "canary" country that is rolled out first and then the other countries follow from that.

graph LR
base --> QA
QA --> us-staging
us-staging --> us-prod
us-prod --> eu-staging --> eu-prod
us-prod --> asia-staging --> asia-prod

All these options are seamless to set up in ConfigHub thanks to the upstream/downstream connections between Config Units and the intelligent incorporation of changes from upstreams via the upgrade process.

If you find you need to propagate changes in a direction not aligned with your clone hierarchy, that's supported, also. You can use the merge source, merge base, and merge end parameters to specify an arbitrary "upstream" to merge a range of revisions from, can use tags to keep track of the revision ranges, and can use a filter to select the mutations eligible to be overridden by the merged changes.