Change Requests

In a production environment, directly editing a secret can be dangerous. A typo could bring down the entire application. RunEnv Change Requests act like "Pull Requests for your Secrets," adding a layer of peer review before changes go live.

Enabling Change Requests

By default, users with Editor or Admin permissions can directly update secrets. To enforce Change Requests:

1. Go to Project Settings > Environments.
2. Edit the target environment (e.g., Production).
3. Toggle Require Change Requests to ON.

The Workflow

Once enabled, the workflow changes:

1. Propose: An engineer modifies a secret in the RunEnv dashboard. Instead of saving immediately, they are prompted to create a Change Request. They can add a title and description explaining why the change is needed.
2. Review: Administrators or designated reviewers receive a notification. They can view a visual diff of the proposed changes (old value vs. new value).
3. Approve & Merge: If the changes are correct, the reviewer approves the request. The new secret values are instantly applied to the environment.
4. Reject: If the changes are incorrect, the reviewer can reject the request with feedback.