Skip to main content

CLI Use Cases

The KDX CLI is not just a wrapper around API calls. It gives platform builders a repeatable way to inspect, promote, test, and operate Kodexa resources without having to click through the UI. Use the CLI when you need a fast feedback loop, a scriptable workflow, or an auditable path from Git to a Kodexa environment.

The Mental Model

Build an Activity Plan Locally

When you are designing an Activity Plan, the CLI helps you keep the resource set together:
For a larger build, use sync manifests so the whole Activity-centered resource set moves together:

Promote a Project Template

Project templates remain useful because they package repeatable project setup. With Activity Plans, a template should bind the project to current plans, task templates, data forms, labels, statuses, service bridges, and document stores.
After creating the project, use kdx get projects, kdx get activity-plans, and kdx get task-templates to confirm that the expected resources exist and are bound.

Test a Document Processing Path

A common development loop is upload, wait, export:
When the export is surprising, download the KDDB file and inspect it locally:

Manage a Metadata Repository

Use kdx sync when resources should live in Git and be promoted through environments.
For CI, let branch and tag mappings decide what deploys:

Inspect the Platform Contract

The CLI discovers resource types from the platform OpenAPI contract. Refresh the local cache after a platform upgrade or when a new resource type is added.
Use kdx run when you need an operation that exists in the API but does not have a dedicated high-level command yet.

Secure Runtime Configuration

Use organization secrets for values that Activity steps and service bridges need at runtime.
Secret values are write-only through the CLI. The list command returns names, not values.

Attach Knowledge Assets

Knowledge items can carry supporting assets such as examples, reference files, evaluation data, or images used in Markdown content.
When you pass --id, the CLI prints the attachment reference that can be used from Markdown content.

Choose the Right Command