CLICommands
l4 config
l4 config reads and writes the CLI's persistent defaults, so you do not repeat the same flags on every command. l4 keeps the config file in the platform-standard config directory (~/.config/levelfour/ on Linux/macOS, %APPDATA%\levelfour\ on Windows).
Subcommands
| Command | Purpose |
|---|---|
list | Show all configuration values and where each one came from |
get <key> | Print one config value |
set <key> <value> | Set a config value |
l4 config list
l4 config get default_provider
l4 config set default_provider awsResolution order
l4 resolves each settable value in this order. The first match wins:
- Command-line flag (e.g.
--provider gcp) - Environment variable (e.g.
LEVELFOUR_API) - Config file (
l4 config set …) - Built-in default
A flag or an environment variable outranks the config file, so a value you set with
l4 config set can sit in the file and never be the one in use. An exported LEVELFOUR_API you have forgotten about sends every command to another host. l4 config list annotates each value with its source, so read that before you decide the file is wrong.Common keys
| Key | Purpose |
|---|---|
default_provider | Default --provider for costs and recommendations |
api_base | Default API base URL (overrides built-in production URL) |
Related
- Authentication: how
l4resolves credentials, and pointing at another API host with--apiorLEVELFOUR_API l4 telemetry: the opt-in flag stored alongside these settings- CLI overview: the flags every command accepts