Secrets, Config, and Troubleshooting

Last validated: 2026-05-20

Secret Commands

Top group:

• dodil ignite secret

Subcommands:

• create <name> --type git|registry ...
• get <name>
• list
• delete <name>

Examples:

dodil ignite secret create github-pat --type git --username alice --token <token>
 
dodil ignite secret create ghcr-creds --type registry --username bot --password <password> --server-address ghcr.io
 
dodil ignite secret list

Security note:

• secret get returns sensitive values. Avoid sending raw output to shared logs.

Config Commands

Top group:

• dodil ignite config

Subcommands:

• init
• view
• set <key> <value>

Valid keys include:

• api_endpoint
• token
• org_id
• output
• debug

Login

dodil login <service_account_id> <service_account_secret>
 
# Optional explicit org default for Ignite commands
dodil ignite config set org_id <org_id>

Optional direct token login remains available:

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

Troubleshooting Checklist

Authentication failures

1. Check dodil ignite config view token and endpoint.
2. Verify DODIL_TOKEN/IGNITE_TOKEN env overrides.
3. Confirm org context (--org or config value) is correct.

Command succeeds but behavior is limited

1. Confirm whether command is a known partial path (for example execution list, run-once, model command caveats).
2. Use API fallback path from coverage doc when needed.

Build or compile issues

1. Check build/compile logs first (build logs, draft compile --follow).
2. Validate context packaging and Dockerfile/build metadata.
3. Confirm backend infra readiness (NATS/object storage/cluster).