Secrets
Secrets stores sensitive runtime configuration under stable Project-owned names. Each value is written as an immutable Secret version; public APIs and the CLI expose metadata without returning the stored value.
Why use Secrets?
Applications need credentials that can change independently of their source and container images. Secrets gives those credentials a separate lifecycle and lets a runtime bind an authorized version when it deploys an application.
What you can do
- Create a named Secret and add versions from a file, an environment variable, or standard input.
- Inspect names, descriptions, status, and version metadata.
- Enable or disable versions as credentials change.
- Bind a Secret or a specific version to a Run Workload environment variable.
Core concepts
A Secret is the stable logical name. A Secret version holds immutable material and its version number. A Run Deployment resolves a logical Secret reference to an enabled version and records that exact version on its Revision.
Permission to inspect metadata does not grant permission to use the value. Runtime use requires the appropriate IAM permission. Code running with a bound Secret can access its value.
Use Secrets
Read the CLI reference for commands or the API reference for resources, request fields, and responses.