Username for control-plane authentication. Sets the `credentials_explicit` flag so the TUI wizard is skipped.
--username <USER> (env: DF_USERNAME)## Overview `--username` provides the account name that the CLI sends to the control plane during authentication. Supplying it together with `--password` (or the equivalent env vars) marks credentials as explicit, which causes the startup TUI to skip the login wizard and the inline stdin prompt to stay silent. The built-in default is `admin@deltaforge.local`, intended for local development only. ## Behavior - The value is sent verbatim as the `username` field of the authentication request. No case folding or trimming is applied beyond what the shell has already done. - Presence of both `--username` and `--password` (through any of the three resolution tiers) sets the internal `credentials_explicit` flag. That flag suppresses the TUI login wizard and the inline credential prompt. - The flag applies to every subcommand that authenticates, including `query`, `run`, `auth`, and the REPL launch. - Token refresh during a long-running REPL session is handled by the HTTP client. The username value is retained for refresh calls. ## Compatibility Resolution order: `--username`, `DF_USERNAME`, profile `username`, built-in default `admin@deltaforge.local`. Profiles can supply a username but never a password; pairing a profile username with `DF_PASSWORD` is a common pattern.
# Explicit credentials on the command line
delta-forge-cli --username admin@company.com --password secret# From a password manager via env vars
DF_USERNAME=service@deltaforge.local DF_PASSWORD=$(pass show df) delta-forge-cli auth# Run a script under a service account
delta-forge-cli -u ci@example.com --password $CI_PASSWORD run deploy/migrate.sql# Combine with a profile: profile supplies URLs, flag supplies identity
delta-forge-cli --profile production --username tahir@example.com --password $DF_PASS query 'SELECT current_user()'