mirror of
https://github.com/coder/coder.git
synced 2026-09-22 05:05:20 +08:00
Zach
85984ff142
Users can now disable a secret to stop it from being injected into workspaces without deleting it, and re-enable it later. Disabled secrets stay visible and editable everywhere they already appear. An enabled secret must have at least one injection target; a secret with no target can be stored only while disabled. Existing target-less secrets are migrated to disabled to preserve current behavior. Support spans the REST API, SDK, CLI, dashboard, and audit log.
33 lines
883 B
Plaintext
33 lines
883 B
Plaintext
coder v0.0.0-devel
|
|
|
|
USAGE:
|
|
coder secret create [flags] <name>
|
|
|
|
Create a secret
|
|
|
|
Provide the secret value with --value or non-interactive stdin (pipe or
|
|
redirect).
|
|
|
|
OPTIONS:
|
|
--description string
|
|
Set the secret description.
|
|
|
|
--enabled bool (default: true)
|
|
Whether the secret is injected into workspaces. An enabled secret must
|
|
set --env or --file; pass --enabled=false to store a secret without
|
|
injecting it.
|
|
|
|
--env string
|
|
Name of the workspace environment variable that this secret will set.
|
|
|
|
--file string
|
|
Workspace file path where this secret will be written. Must start with
|
|
~/ or /.
|
|
|
|
--value string
|
|
Set the secret value. For security reasons, prefer non-interactive
|
|
stdin (pipe or redirect).
|
|
|
|
———
|
|
Run `coder --help` for a list of global options.
|