Reference

References for every Dexaflow surface — the HTTP API, CLI, Go packages, Python runtime, configuration, and MCP server.

References for every Dexaflow surface. The HTTP API, CLI, Go, and Python references are generated from source on every push, so they never drift from the code. The tables of the Configuration and Metrics pages are generated from internal/config and from the registered collectors, and a test fails while either page is stale.

The Glossary collects the core vocabulary (DAG, DagRun, XCom, Executor, …).


HTTP API (Scalar)

The /api/v2/ control-plane API, Airflow 3.2.x-compatible, as an interactive Scalar reference generated from the OpenAPI spec.

CLI reference

Every dexaflow command and flag, generated from Cobra.

Go packages (GoDocs)

GoDocs for the control plane, scheduler, executor, agent, and storage — one page per package.

Python runtime API

The leoflow_runtime package that runs your task callable inside the container and bridges its return value to XCom.

Configuration

The DEXAFLOW_* environment variables and config keys for the server.

Metrics

Every Prometheus metric family the control plane exports, with its type, labels and meaning.

Compatibility

The platforms Dexaflow runs on and talks to, per release line, and whether each is tested in CI, supported or best effort.

Published images

Every container image and chart Dexaflow publishes, how each is tagged, and which tags are immutable.

Glossary

The core Dexaflow vocabulary — DAG, Task, TaskInstance, DagRun, XCom, Executor, Agent — kept compatible with Airflow.

MCP server

The Dexaflow MCP server now has its own top-level section.