${SECRET_NAME} syntax.
Commands
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
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:secrets delete
Prompts for confirmation; pass--yes (-y) in scripts and CI.
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.