mirror of
https://github.com/coder/coder.git
synced 2026-09-22 05:05:20 +08:00
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.
35 lines
1.1 KiB
Plaintext
35 lines
1.1 KiB
Plaintext
coder v0.0.0-devel
|
|
|
|
USAGE:
|
|
coder secret update [flags] <name>
|
|
|
|
Update a secret
|
|
|
|
At least one of --value, --description, --env, --file, or --enabled must be
|
|
specified. Provide the secret value by at most one of --value or
|
|
non-interactive stdin (pipe or redirect).
|
|
|
|
OPTIONS:
|
|
--description string
|
|
Update the secret description. Pass an empty string to clear it.
|
|
|
|
--enabled bool
|
|
Whether the secret is injected into workspaces. An enabled secret must
|
|
keep at least one of --env or --file; pass --enabled=false to stop
|
|
injecting it without deleting it.
|
|
|
|
--env string
|
|
Name of the workspace environment variable that this secret will set.
|
|
Pass an empty string to clear it.
|
|
|
|
--file string
|
|
Workspace file path where this secret will be written. Must start with
|
|
~/ or /. Pass an empty string to clear it.
|
|
|
|
--value string
|
|
Update the secret value. For security reasons, prefer non-interactive
|
|
stdin (pipe or redirect).
|
|
|
|
———
|
|
Run `coder --help` for a list of global options.
|