`fluid export`

Export a FLUID contract as executable orchestration code (Airflow DAG, Dagster pipeline, or Prefect flow).

Syntax

fluid export CONTRACT [--engine ENGINE] [--output-dir DIR] [--provider PROVIDER] [--env ENV] [-v]

Key options

Option	Description
`CONTRACT`	Path to FLUID contract file (YAML or JSON).
`--engine`	Orchestration engine: `airflow`, `mwaa`, `dagster`, or `prefect`. Default `airflow`.
`--output-dir`, `-o`	Output directory for generated files. Default `.` (current directory).
`--provider`	Override provider (`aws`, `gcp`, `azure`, `snowflake`). Default auto-detected from `contract.provider`.
`--env`	Environment overlay to apply (e.g. `dev`, `test`, `prod`).
`--verbose`, `-v`	Verbose output, including file stats and next-step hints.

Examples

fluid export contract.yaml --engine airflow -o dags/
fluid export contract.yaml --engine dagster -o pipelines/
fluid export contract.yaml --provider aws --engine airflow -o dags/
fluid export contract.yaml --engine airflow --env prod -o dags/prod/

Notes

The contract must contain an orchestration.tasks section; otherwise the command fails with missing_orchestration.
Code generation is delegated to the active provider's export() method. Providers that lack export() (commonly local-only providers) will fail with export_not_supported.
Step Functions output is reserved for a future release and is not currently selectable.
For exporting the contract itself in standards-compliant formats, see fluid odps, fluid odps-bitol, fluid odcs, and fluid export-opds.