lizard secrets
Manage a project’s or service’s secrets (environment variables).
Usage
lizard secrets <subcommand> [args] [flags]Subcommands
lizard secrets set <K=V>...
Set one or more secrets (variadic). Default scope is the service; --global targets the project.
| Flag | Description |
|---|---|
--global | Project scope |
-s, --service <name> | Service scope |
lizard secrets list
List secrets in scope.
| Flag | Description |
|---|---|
--show | Reveal values |
--ref | List the ${{…}} references available in this scope |
lizard secrets delete <K>...
Delete one or more secrets (variadic, alias rm). It asks for confirmation; without a TTY, pass -y.
| Flag | Description |
|---|---|
-y, --yes | Skip confirmation |
lizard secrets import
Import KEY=value lines from stdin. It skips blank lines and lines starting with #. Quotes stay part of the value; remove any export prefixes first.
Examples
Set secrets on the linked service
lizard secrets set DATABASE_URL=postgres://… LOG_LEVEL=info
lizard secrets set API_KEY=sk_live_… --service apiSet a project-wide secret
lizard secrets set NODE_ENV=production --globalList and reveal secrets
lizard secrets list
lizard secrets list --showDelete secrets
lizard secrets delete OLD_KEY ANOTHER_KEY
lizard secrets delete OLD_KEY --yes # in CI or a scriptImport a .env file
lizard secrets import < .envSee also
- Variables & secrets — scoping, precedence, and build-time vs. runtime behavior
- Cross-service references — read one service’s values from another
- Troubleshooting: a secret or reference isn’t showing up
- lizard run — run a command locally with project + service secrets injected
Updated