LakeQL
Overview
  • Installation
Commands
  • init
  • pull
  • create-registry
  • create-endpoint
  • generate-import-config
  • list-schemas
  • list-tables
  • list-views
  • list-columns
  • add
Configuration
  • Environment Variables
  • Config File
GitHub
LakeQL
  1. CLI
  2. Configuration
  3. Environment Variables

On this page

  1. Loading an Env File
  2. CLI Log Level

Environment Variables

The environment the CLI reads, and the —env option.

The CLI connects to the data source to introspect and generate. It needs the same environment your lakeql.config.ts references: data source hosts, credentials, and so on.

Loading an Env File #

Every command accepts the global --env [path] option. It loads an env file into the environment before the config is read, so a config that references env.* resolves its values:

pnpm lakeql-cli pull --env .env
  • Given without a value, --env defaults to .env .
  • Relative paths resolve against the directory you ran the command from.
  • Loading uses Node's built-in .env parser, so there is no extra dependency.
  • A missing or unreadable file is a hard error, because you asked for it explicitly. Omit --env to use the ambient environment instead.

CLI Log Level #

LOG_LEVEL controls the CLI's own verbosity. Set it to debug, info, warn, or error. It defaults to warn.

1
2
LOG_LEVEL=debug lakeql-cli pull --env .env

Previous page

Configuration

Next page

Config File