Secrets · Guides
Roll back a change
Every change to an environment is numbered and kept, with the values as they were. Any one can be put back, and putting it back is a change too.
The history
An environment's History tab lists its changes, newest first, by day, 30 to a page. Each is numbered from #1 in its environment and says who made it and when:
- Added, Changed or Removed, with the variable's name,
- Imported, with the names it added and changed: a pasted
.env, or keys that id.my-beast.com wrote for your other My Beast products, - Rolled back, with the change it put back.
For a Visible variable each change shows the old and the new value; for a Secret one, the name only. See Values in the history.
If the project also has Errors, an issue's page names the changes made to its environment in the hour before it, names only, each linked to its place in this history. A changed variable is often why something broke right after.
Roll back a change
Choose Roll back #12 beside the change. It asks first, naming what comes back and what goes. Then every name the change touched goes back to what it was before it:
- a name it added is removed,
- a name it changed gets its old value back,
- a name it removed comes back, with its value.
The roll back is a new change, Rolled back #12, so it can be rolled back too. The change it put back is marked Rolled back in #13. Rolling back takes Triage or Admin in the environment.
Values are never opened to roll back
When a roll back isn't offered
- A later change touched the same names. The change says Changed again later: and names them, each with the change that touched it. Roll that later one back first, or change the names by hand.
- It was rolled back already. It says Rolled back in and the change that did it. To have it again, roll that one back.
Machines after a roll back
A machine gets the values back from its next read, like any change. Until then its token is marked Behind on the Tokens page: see Where each token stands.