Quickstart, Auth, and Command Model

Last validated: 2026-05-20

Invocation Model

Primary usage in this docs set uses plugin style:

dodil ignite <command>

Standalone binary usage is equivalent:

ignite <command>

Quickstart

# Recommended: authenticate once at shared Dodil CLI level
dodil login <service_account_id> <service_account_secret>
 
# Optional: set/override Ignite org default for shorter app IDs
dodil ignite config set org_id <org_id>
 
# Validate config
dodil ignite config view
 
# Basic smoke calls
dodil ignite app list
 
dodil ignite models list

Optional direct-token mode (useful for isolated testing):

dodil ignite login --token <bearer_token> --api-endpoint api.dodil.io:443 --org <org_id>

App ID Format

Most app-targeted commands accept:

• org:app explicit format
• app only (org resolved from config/flags)

Examples:

dodil ignite app get hello

Global Flags

Common flags from root command:

• --output, -o
• --api-endpoint
• --token
• --org
• --org-name (dev/test only)
• --debug
• --timeout
• --config

Config and Env Precedence

Token resolution order:

1. --token
2. DODIL_TOKEN
3. IGNITE_TOKEN
4. Config file token

Other key env vars:

• IGNITE_API_ENDPOINT
• IGNITE_ORG_ID
• IGNITE_ORG_NAME
• IGNITE_DEBUG

Config directory search priority:

1. DODIL_CONFIG_DIR
2. IGNITE_CONFIG_DIR
3. ~/.config/unified-cli
4. ~/.ignite

Practical Notes

1. dodil login writes shared auth/config under ~/.config/unified-cli/config.yaml, which Ignite CLI can consume.
2. dodil ignite login is optional and mainly useful for explicit token testing/overrides.
3. --org-name is for direct/dev testing flows; production org context should come from validated auth metadata path.
4. Output default can vary by config/init flow (table default in root, json often set by login/init paths).
5. Keep --timeout realistic for streaming and build operations to avoid client-side early cancellation.