Secrets

Not yet available

This feature is on the roadmap and cannot be used today. Until it ships, manage credentials in your own secret store.

Secrets will provide managed storage for the credentials your workloads need — third-party API keys, database URLs, registry tokens — so they can be referenced by name instead of pasted into a configuration.

How we expect it to work

1. Store a secret under a name, scoped to your workspace.
2. Reference it by name from a managed app, deployment or job.
3. Rotate it in one place, and every workload picks up the new value.

What we expect to hold true

• Write-only: once stored, a secret can be referenced and replaced but not read back through the UI or API.
• Encrypted at rest, and injected into workloads at run time rather than baked into images.
• Access follows workspace roles.
• Rotation without redeploying every consumer.

Note this is for secrets your workloads consume. Your ResetData API keys are managed separately, under API keys — see Authentication.