Define and implement CLI for user-secrets #791
Description
There are 2 places where we can place CLI commands:
- cli/
- enterprise/cli/
In our case they should be placed in cli/
Implementation should take into account that later it will be extended with org-secrets and org-level options such as:
--type <user|organization>[--org <organization-name>]
CLI Definition
# Create a user secret
coder secrets create <name>
--value <secret-value>
[--description <description>]
[--inject-env <ENV_VAR_NAME>]
[--inject-file <path/to/file>]
# Update a user secret
coder secrets update <name>
--value <new-secret-value>
[--description <new-description>]
[--inject-env <ENV_VAR_NAME>]
[--inject-file <path/to/file>]
# Get a user secret metadata (without value)
coder secrets get <name>
# List user secrets metadata
coder secrets list
# Delete a user secret
coder secrets delete <name>
Aliases (to be consistent with templates and tokens commands):
secrets -> secret