Secrets
Your application environment variables!
secrets:create
seekritCreates or overrides a secret under an environment. Prompts if no input.
USAGE
$ seekrit secrets:create
OPTIONS
-e, --environment=environment Name of environment.
-n, --name=name Name of new secret.
-o, --organization=organization Name of organization.
-p, --project=project Name of project.
-v, --value=value Value of new secret to store.
secrets:list
seekritLists all secrets under a specified environment. Prompts if no input.
USAGE
$ seekrit secrets:list
OPTIONS
-e, --environment=environment Name of environment.
-f, --format=table|.env|.yaml [default: .env] Format to list secrets
-o, --organization=organization Name of organization.
-p, --project=project Name of project.
secrets:delete
seekritDeletes a secret from an environment. Prompts if no input.
USAGE
$ seekrit secrets:delete [NAME]
ARGUMENTS
NAME Name of secret to delete.
OPTIONS
-e, --environment=environment Name of environment.
-o, --organization=organization Name of organization.
-p, --project=project Name of project.
secrets:import
seekritImports environment variables from a .env or .yaml file to create or override secrets under an environment. Prompts if no input.
USAGE
$ seekrit secrets:import [PATH]
ARGUMENTS
PATH Path of .env or .yaml file to import
OPTIONS
-e, --environment=environment Name of environment.
-o, --organization=organization Name of organization.
-p, --project=project Name of project.
Examples of import files
Below is an example of a correctly structured env files ready for import.
.env
hello=world
key=value
.yaml
hello: 'world'
key: 'value'
run
seekritExecutes given command and injects specified secrets into its environment.
USAGE
$ seekrit run [flags] -- "COMMAND"
ARGUMENTS
COMMAND Command to execute with secrets injected into its environment. Must be wrapped in quotes.
OPTIONS
-e, --environment=environment Name of environment.
-o, --organization=organization Name of organization.
-p, --project=project Name of project.
EXAMPLE
$ seekrit run -o org -p project -e env -- "printenv"
Looking to automate this workflow?
We have created commands within our CLI to give you the ability to set as many default environments, organizations, and projects as needed. So that you can automate your workflow. Click here to learn more.
← Environments Teams →