Lade (/leɪd/) is a tool allowing you to automatically load secrets from your preferred vault into environment variables or files. It limits the exposure of secrets to the time the command requiring the secrets lives.
Lade is part of the Metatype ecosystem. Consider checking out how this component integrates with the whole ecosystem and browse the documentation to see more examples.
You can download the binary executable from
releases page on GitHub, make it
executable and add it to your $PATH or use the method below to automate those
steps.
# recommended way
curl -fsSL https://raw.githubusercontent.com/zifeo/lade/main/installer.sh | bash
# or alternative ways via cargo
cargo install lade --locked
cargo install --git https://github.com/zifeo/lade --locked
# upgrade
lade upgrade
# install shell hooks (only required once)
lade installCompatible shells: Fish, Bash, Zsh
Compatible vaults: Infisical, 1Password CLI, Doppler, Vault
Lade will run before and after any command you run in your shell thanks to
command hooks installed by lade install. On each run, it will recursively look
for lade.yml files in the current directory and its parents. It will then
aggregate any secrets matching the command you are running using a regex and
load them into environment variables or files for the time of the run.
cd examples/terraform
terraform apply
# example = "hello world"See lade.yml or the examples folders for other uses cases.
In case you prefer to decide when to load secrets, you can manually decide when
to inject them using the inject command. Note that when running scripts or a
non-interactive shell session, there is no guarantee that the shell hooks will
be triggered. In that case, the inject command is the only way to load
secrets.
cd examples/terraform
lade inject terraform applyBy default, Lade will load secrets into environment variables. You can change
this by setting the . to the desired file name. The content will be created
based on the extension. Currently, only YAML and JSON are supported.
command regex:
.: file.yml
...In the case where you have different secrets for different users, you can specify a different secret for each user by specifying each user as a key under a variable.
command regex:
SAME_SECRET_FOR_EVERYONE: hello_world
SECRET_FOR_THE_USER:
alex: alex_secret
zifeo: zifeo_secretLade will use the current user by default. you can change this by setting the
user subcommand.
lade user # get currently set user
lade user tonystark # set user to tonystark
lade user --reset # reset user, fallback to current userMost of the vault loaders use their native CLI to operate. This means you must have them installed locally and your login/credentials must be valid. Lade may evolve by integrating directly with the corresponding API, but this is left as future work.
command regex:
EXPORTED_ENV_VAR: infisical://DOMAIN/PROJECT_ID/ENV_NAME/SECRET_NAMEFrequent domain(s): app.infisical.com.
Note: the /api is automatically added to the DOMAIN. This source currently
only support a single domain (you cannot be logged into multiple ones).
command regex:
EXPORTED_ENV_VAR: op://DOMAIN/VAULT_NAME/SECRET_NAME/FIELD_NAMEFrequent domain(s): my.1password.eu, my.1password.com or my.1password.ca.
command regex:
EXPORTED_ENV_VAR: doppler://DOMAIN/PROJECT_NAME/ENV_NAME/SECRET_NAMEFrequent domain(s): api.doppler.com.
command regex:
EXPORTED_ENV_VAR: vault://DOMAIN/MOUNT/KEY/FIELDcommand regex:
EXPORTED_ENV_VAR: passbolt://DOMAIN/RESOURCE_ID/FIELDSupports INI, JSON, YAML and TOML files.
command regex:
EXPORTED_ENV_VAR: file://PATH?query=.fields[0].fieldPATH can be relative to the lade directory, start with ~/$HOME or absolute
(not recommended when sharing the project with others as they likely have
different paths).
command regex:
EXPORTED_ENV_VAR: "value"Escaping a value with the ! prefix enforces the use of the raw loader and
double !! escapes itself.
eval "$(lade off)"
eval "$(cargo run -- on)"
echo a $A1 $A2 $B1 $B2 $B3 $C1 $C2 $C3
cargo run -- -vvv set echo a
cargo run -- inject echo a
eval "$(cargo run -- off)"
eval "$(lade on)"