fnox export

• Usage: fnox export [FLAGS] [KEY]…
• Aliases: ex

Print or write resolved secrets as env, shell, JSON, YAML, or TOML

Resolves the active profile's secrets and prints them in the chosen format, or writes them to --output. By default only secrets with env = true are included, matching shell integration; --all adds env = "exec" and env = false secrets. An as_file secret is exported as the path of a temporary file that holds its value.

Name one or more KEYs to export only those secrets. Only the named secrets are resolved, so other secrets cost no provider calls or auth prompts. Naming a key includes it whatever its env setting, so --all is not needed. An unknown key is an error.

JSON, YAML, and TOML put the values in a secrets object, which fnox import reads back. The output contains real values, and --output creates the file with your default permissions, so set a restrictive umask first.

Arguments

• [KEY]… — Secrets to export; all eligible secrets when omitted

Flags

• -f --format <FORMAT> — Output format

  Choices: env, shell, json, yaml, toml

  Default: env

• -n --dry-run — With --output, list the keys instead of writing the file

  Has no effect on output to stdout, which still contains the values.

• -o --output <OUTPUT> — Write to this file instead of stdout

• --all — Include secrets with env = false or env = "exec"

• --header — Start env and shell output with comments naming the profile, time, and count

• -h --help — Print help

Examples

Print dotenv lines

fnox export

Print JSON

fnox export --format json

Export only some secrets

fnox export --format json DATABASE_URL API_KEY

Load secrets into the current shell

eval "$(fnox export --format shell)"

Write a private .env file

(umask 077 && fnox export -o .env)

See also

• Import and export