infisical run
The command that injects your secrets into local environment
Description
Inject secrets from Infisical into your application process.
Subcommands & flags
infisical run
infisical run
Use this command to inject secrets into your applications process
Environment variables
INFISICAL_TOKEN
INFISICAL_TOKEN
Used to fetch secrets via a service token apposed to logged in credentials. Simply, export this variable in the terminal before running this command.
INFISICAL_DISABLE_UPDATE_CHECK
INFISICAL_DISABLE_UPDATE_CHECK
Used to disable the check for new CLI versions. This can improve the time it takes to run this command. Recommended for production environments.
To use, simply export this variable in the terminal before running this command.
Flags
--project-config-dir
--project-config-dir
Explicitly set the directory where the .infisical.json resides. This is useful for some monorepo setups.
--command
--command
Pass secrets into multiple commands at once
--token
--token
If you are using a service token to authenticate, you can pass the token as a flag
You may also expose the token to the CLI by setting the environment variable INFISICAL_TOKEN
before executing the run command. This will have the same effect as setting the token with --token
flag
--expand
--expand
Turn on or off the shell parameter expansion in your secrets. If you have used shell parameters in your secret(s), activating this feature will populate them before injecting them into your application process.
Default value: true
--env
--env
This is used to specify the environment from which secrets should be retrieved. The accepted values are the environment slugs defined for your project, such as dev
, staging
, test
, and prod
.
Default value: dev
--secret-overriding
--secret-overriding
Prioritizes personal secrets with the same name over shared secrets
Default value: true
--tags
--tags
--path
--path
The --path
flag indicates which project folder secrets will be injected from.