Versions, revisions, and snapshots

Inspect a secret's history

Open an environment, select a secret's history action, and review its versions. History identifies creation, edits, imports, and restores. Values remain hidden until you explicitly reveal or copy a version; those actions are audited.

Use the current marker and version number to understand what the application will receive on its next read. A previously revealed value on your screen is not automatically updated when someone changes the secret.

Restore an earlier value

Choose a historical version and Restore version, then review any production confirmation. From the CLI:

outray secrets rollback DATABASE_URL --version 2

Rollback restores the historical value through the normal versioned mutation workflow; it does not delete intervening history. If the requested value is already current, the CLI reports that no change is needed. Conflicts are checked against the current secret version and environment revision, so refresh after a concurrent edit rather than guessing the next version.

Running processes do not automatically reread environment values. Restart the application, redeploy it, or use CLI watch mode when that restart workflow is appropriate.

Understand the environment revision

An environment revision is a change counter used for concurrency checks and watch mode. It is not a named backup, whole-environment historical version, or command to restore an entire environment. Per-secret history is the supported value-restoration workflow.

Share snapshots are separate copies

Creating a share reads selected values and records their versions before encrypting an independent snapshot in the browser. Later edits, moves, or deletion of the source values do not update that link's content.

The dashboard checks that selected versions have not changed during share creation. If it reports that the selection changed, refresh the source and create a new snapshot. Do not reuse a link expecting it to show current credentials after rotation.

Revoking a share stops future reveals from that link, but it cannot erase plaintext a recipient already copied. Rotate the underlying credential separately if disclosure is no longer acceptable.