Update a shared environment variable

Including what to do when a branch is out of date.

By the OneEnv team · Last updated 2026-10-15

Before you start

• Find who depends on the variable: open Env Master or the Dependency Graph, or the Report's services view.
• Decide the branch name after the reason, such as rotate-db-host, so the History page reads well.

Steps

1. Create or select a branch.
2. Edit the value in Env Master and save. Secret values you did not change must not be re-submitted as the masked display text; OneEnv rejects that.
3. Open the branch and read the Change Review Center before submitting: the impact matrix lists the services that would be notified, and readiness flags conflicts.
4. Submit for review. An Owner or Admin approves and merges.
5. Tell the owners of the listed services to expect a decision, in whatever channel your team uses; notification email or webhook is opt-in per member.
6. Each service approves when it is ready to take the value. Until it does, its export keeps the old value.

Stale branch

If another branch changed the same variable first, your branch shows a conflict. Rebase refreshes the 'before' value to the current one. Check the diff again: you are now replacing the newer value.

Service-specific exceptions

A service that must keep a different value sets an override and publishes it from its own page. An override wins over any shared value for that service and does not go through a branch.