19 · Secrets, scoped registry
Secrets and registries
Secrets injected at run time, never written to a file.
Secrets reach a process from a vault through its environment and are never written to disk; the cloud key vault is a checked projection of that vault; and every image reaches the registry through one tool that keeps each product's access scoped.
- 01Run with secrets, write no file — one command puts secrets in a process's environment, with a names-only check mode.
- 02One root, one projection — the cloud key vault is seeded from the password vault, and a read-only check reports drift.
- 03One gate for images — the push tool validates the repository name, uses a short-lived token and stores no credentials.
- 04Scoped grants — a read grant for one product's namespace cannot reach another's.
- 05Commit-time backstop — a pre-commit hook blocks committed secret files.
Internal
- 21 secret manifests
- 6 test suites
- 10 tool contracts
SurfacesCLI
- Bitwarden
- Azure Key Vault
- Azure Container Registry
- Bicep
- Bash
- pre-commit