Manage a change affecting multiple services
When one branch has many consumers who answer at different speeds.
By the OneEnv team · Last updated
Scenario
One branch contains a new host (env), a new column (database) and a route path change (API). Five services are affected, owned by different people.
Steps
- Group related edits on one branch so the reviewer sees the whole change. Keep unrelated edits on separate branches so one rejection does not block the rest.
- In the Review Center check the summary per domain, the impact matrix, readiness, and the 'blocks' list of other open branches touching the same items.
- After merge, Notifications groups the fan-out under the branch. Each service's owner (or any service_admin) decides separately.
- Services may answer at different speeds. Un-actioned services keep serving their last approved values.
- Use Report and History to find unresolved decisions and who made each.
Partial approval
This is normal. The change is merged in the masters; each service is individually on the new or the old value. The masters and a service's accepted state can differ for a while, deliberately.
If a service must not accept
It rejects. For env values the service stays on its last approved value; for routes and rules it is marked diverged. A later change to the same item supersedes the older pending decision.