Manage vault secrets from the command line. Store credentials for authenticated monitor checks and use them in config-as-code withDocumentation Index
Fetch the complete documentation index at: https://docs.devhelm.io/llms.txt
Use this file to discover all available pages before exploring further.
${SECRET_NAME} syntax.
Commands
| Command | Description |
|---|---|
devhelm secrets list | List all secrets (names only, values are hidden) |
devhelm secrets create | Create a new secret |
devhelm secrets update <key> | Update a secret’s value |
devhelm secrets delete <key> | Delete a secret |
Secrets are identified by key (e.g.,
SLACK_WEBHOOK_URL). Secret values are write-only — you can set and delete them, but never read the plaintext value back.secrets list
secrets create
| Flag | Type | Required | Description |
|---|---|---|---|
--key | string | Yes | Secret name |
--value | string | Yes | Secret value |
Environment scoping for secrets is supported in the API and the YAML file format (see YAML reference), but the CLI
secrets create command does not yet expose an --environment flag. To create environment-scoped secrets from a config-as-code workflow, define them in devhelm.yml and run devhelm deploy.secrets update
Update an existing secret’s value:| Flag | Type | Required | Description |
|---|---|---|---|
--value | string | Yes | New secret value |
secrets delete
Using secrets in config
Reference secrets in yourdevhelm.yml with ${...} syntax:
Next steps
Environments
Create environments for secret scoping.
Monitoring as Code
Use secrets in your YAML config.