Version control for environment variables
Environment variable version control with safe rollback
RunEnv turns environment configuration changes into an inspectable operating history. Compare the shape of environments, review sensitive changes, and restore an available version when a bad value needs to be reversed.
The workflow
A clearer operating model for configuration.
Each page is grounded in a workflow RunEnv supports today. Use the examples and documentation links to decide whether the model fits your team.
Keep history when values change
Supported updates create a new secret version while preserving the previous row as history. The record includes the change context available to the caller, so teams can inspect what happened and when instead of relying on an overwritten file.
- Open secret history from the dashboard to review available versions.
- Use retention settings to understand how long history remains available.
- Keep the current value and the recovery path in the same environment workflow.
Compare before promoting
Environment diff and promotion workflows let a team see which keys are new, changed, removed, or already aligned before moving a change toward another environment. That makes staging-to-production handoffs easier to explain and review.
- Filter the comparison to the differences that need attention.
- Review a selected change set before it overwrites the target environment.
- Capture a snapshot and audit receipt around controlled promotion workflows.
Add a human control point for production
Change Requests can require review before sensitive environment changes go live. Reviewers see a visual diff, can approve or reject the proposal, and the activity is recorded in audit history.
- Require Change Requests on a production environment.
- Explain why a change is needed before it is approved.
- Keep proposal, approval, rejection, and comment activity together.
Restore an available previous version
When an authorized user finds a bad value, the Secret History workflow can restore an available previous version. Restoration creates a new version rather than erasing the record of the rollback.
How it works
Start with the boundary your team needs.
- 01
Make the proposed change
Update the configuration in the environment where the change belongs, with the access and workflow required by that environment.
- 02
Compare and review the delta
Use environment diff, snapshots, or a Change Request to make the affected keys and decision path visible before promotion.
- 03
Promote or restore deliberately
Apply the approved change, or restore an available version while preserving a new version and the surrounding audit history.
Continue learning
Read the implementation details.
The documentation explains the supported commands, permissions, retention boundaries, and delivery modes behind this workflow.