Before you start
- The upstream blueprint runs Vault in development mode with an in-memory root token. Replace it with persistent storage, TLS, and an operator-owned init/unseal procedure; do not use it as production Vault.
- vault: command interpolation needs an explicit environment-aware startup adapter
- vault: review Compose cap_add=['IPC_LOCK']; no implicit host privileges or configuration mounts
Configuration that needs your attention
This migration candidate preserves supported service, storage and credential declarations. Resolve every prerequisite before deployment.
Candidate credential references
This draft lists possible credential bindings. Some providers are alternatives. Finalize the required bindings after resolving the migration prerequisites; do not create every listed provider account.
-
vault-dev-root-token-id
Complete the prerequisites
This migration is not enabled for deployment. Resolve the prerequisites listed above and validate startup, networking and persistent storage before using it.