Skip to main content
Antideploy has no separate secrets feature, because it does not need one: every environment variable is already stored as a secret.

​
One store

There is no second, weaker place to put a value. Everything you set goes to the same place and gets the same treatment. This is why the dashboard shows one panel called Environment variables and the API endpoint is called /api/v1/secrets. Same store, two names.
Because values cannot be read back, keep your own copy of anything you cannot regenerate. If you lose a value you did not save elsewhere, the only way forward is to issue a new credential and set it again.

​
Reading them in your app

Secrets arrive as ordinary environment variables. There is nothing to mount, unseal, or call.

​
Rotating a credential

1

Issue the new credential

Create it in the provider: Stripe, your OAuth app, wherever it comes from. Leave the old one active for now.
2

Set the new value

Update it in the dashboard, or PUT it over the API. Storing it does not change what the running app is using.
3

Redeploy

The new value reaches your app when it next starts. Until then the running container still holds the old one.
4

Revoke the old credential

Once the new deployment is live and healthy, revoke the old one at the provider.
The redeploy in step three is not optional. A container’s environment is fixed for the life of that revision; there is no mechanism that swaps a value under a running app.

​
What is not tracked

Antideploy does not keep an audit log. There is no record of who read, set, or deleted a value, and no access history to review after an incident.If you need that, treat the credential’s own provider as the source of truth: most will show you when a key was last used.
Deleting an application deletes its stored values along with everything else it owned.

Environment variables

Setting values, and the ones Antideploy injects for you.