Skip to Content
We are live but in Staging 🎉
WorkflowsPrerequisites and Shared Setup

Prerequisites and Shared Setup

Use this setup before running any workflow in this folder.

Required Inputs

  • <token>: bearer token
  • <org_id>: organization ID
  • <bucket>: target bucket name

API endpoint used in examples:

  • https://k3.dev.dodil.io

CLI note:

  • After dodil login, the CLI reads endpoint/token/org defaults from ~/.config/dodil/config.yaml, so workflow commands use short form dodil k3 ....
  • To override endpoint for a single command, add --api-endpoint "https://k3.dev.dodil.io".

Environment Setup

export K3_TOKEN="<bearer_token>" export K3_ORG="<org_id>" export K3_BUCKET="<bucket>"

Optional CLI defaults helper:

alias k3='dodil k3'

Quick Connectivity Checks

dodil k3 bucket list curl -sS "https://k3.dev.dodil.io/health" \ -H "Authorization: Bearer $K3_TOKEN" \ -H "x-organization-id: $K3_ORG"

Reusable cURL Headers

AUTH=(-H "Authorization: Bearer $K3_TOKEN" -H "x-organization-id: $K3_ORG") JSON=(-H "Content-Type: application/json")

Validation Checklist

  1. Token is valid and not expired.
  2. Org ID matches the target resources.
  3. Endpoint is reachable from your network.
  4. For object uploads via CLI, endpoint includes https:// scheme.

Next: Source to Ingest Pipeline Flow