fluid generate

Unified artifact generation from FLUID contracts.

Syntax

fluid generate <transformation|speed-transformation|dbt|dbt-tests|schedule|ci|standard|artifacts>

Subcommands

fluid generate artifacts

Stage 3 of the 11-stage pipeline. Fanout that produces all catalog + execution artifacts for a contract in one call:

• ODCS (v3.1.0) contract files under odcs/
• ODPS-Bitol (v1.0.0) product files under odps-bitol/
• Schedule DAGs under schedule/ (Airflow / Dagster / Prefect — depending on orchestration.engine)
• Policy bindings under policy/bindings.json (IAM / GRANT)
• A unified MANIFEST.json (SHA-256 per file + merkle root) for downstream stage-4 verification

Reference-only contracts (builds[].pattern: hybrid-reference / reference / external-reference) auto-skip the schedule and policies emitters — those execution artifacts are owned by the team's own dbt/Airflow repo. Catalog artifacts (odcs/, odps-bitol/) are still emitted.

Key options:

• CONTRACT — path to contract.fluid.yaml (or a tgz bundle from fluid bundle --format tgz)
• --out PATH — output directory (default dist/artifacts/)
• --emit {odcs,odps-bitol,schedule,policies}[,...] — explicit emit set; default emits all of these
• --env ENV — environment overlay
• --no-generate-artifacts — CI helper: auto-skip this stage when the contract is reference-only (pattern: hybrid-reference etc.)

fluid generate artifacts contract.fluid.yaml --out dist/artifacts/
fluid generate artifacts runtime/bundle.tgz --out dist/artifacts/        # tgz input
fluid generate artifacts contract.fluid.yaml --emit odcs,odps-bitol      # catalog only

Verify the emitted tree with fluid validate-artifacts (stage 4).

fluid generate transformation

Generate transformation artifacts such as dbt projects or SQL output.

Key options:

• contract
• --output, -o
• --build-index
• --overwrite
• --env
• --dbt-validate
• --list
• --verbose

When the contract was produced by fluid forge data-model, the generator auto-loads the logical sidecar named by labels.modelSidecar and emits deterministic SQL from the forged logical model. For dbt output, zero generated models/**/*.sql files is a hard failure rather than a quiet success.

A normal dbt output directory includes:

• dbt_project.yml
• profiles.yml
• models/sources.yml when source hints are available
• non-empty SQL models under models/

fluid generate speed-transformation and fluid generate dbt remain aliases for this path.

fluid generate dbt-tests

Read the contract's exposes[].contract.dq.rules[] and emit a dbt schema.yml so your data-quality rules run as native dbt tests.

fluid generate dbt-tests
fluid generate dbt-tests contract.fluid.yaml -o dbt/models/schema.yml
fluid generate dbt-tests --env prod

Key options:

• Column-level rules map to dbt's built-in tests — not_null, unique, accepted_values — with dbt-utils placeholders emitted for rules that have no native dbt equivalent.
• Model-level rules map to dbt-utils: anomaly_detection / drift_detection rules become dbt-utils expressions, and a freshness rule becomes dbt_utils.recency.
• The generated dbt-utils-based tests require the dbt-utils package to be installed in your dbt project.
• A managed-by sentinel marks the generated file, so re-running the command never clobbers a schema.yml you have hand-edited.

After generating, run dbt test in your dbt project to execute the rules.

fluid generate schedule

Generate orchestration artifacts such as Airflow DAGs, Dagster pipelines, or Prefect flows.

Key options:

• contract
• --output, -o
• --scheduler
• --overwrite
• --env
• --list
• --verbose

This is the promoted path for orchestration generation.

fluid generate ci

Generate CI/CD pipeline configuration for Jenkins, GitHub Actions, GitLab CI, Azure DevOps, Bitbucket, CircleCI, or Tekton.

Key options:

Jenkins example for an Entropy Data / Data Mesh Manager first run:

fluid generate ci contract.fluid.yaml \
  --system jenkins \
  --install-mode pypi \
  --default-publish-target datamesh-manager \
  --no-verify-strict-default \
  --publish-stage-default \
  --no-publish-include-env \
  --out Jenkinsfile

fluid generate standard

Export to data product standards.

Key options:

• contract
• --format, -f
• --out, -o
• --env
• --list

Supported formats:

Examples of each format

fluid generate standard contract.fluid.yaml --format odps        # FLUID -> Bitol ODPS v1.0.0 (default, center-stage)
fluid generate standard contract.fluid.yaml --format odcs        # FLUID -> ODCS v3.1.0
fluid generate standard contract.fluid.yaml --format odps-v4.1  # FLUID -> LF/ODPI ODPS v4.1 (opt-in)
fluid generate standard contract.fluid.yaml --format odps-bitol  # FLUID -> ODPS (strict Bitol conformance)

ODPS environment tuning

The ODPS exporter reads a few environment variables for output shape:

All formats are deterministic — identical input yields byte-identical output, so the result is safe to check into version control.

Shortcut — fluid export-odps

For a one-shot file write of the ODPS format:

fluid export-odps CONTRACT [--env ENV] [--out PATH]

Produces the same output as fluid generate standard --format odps.

Examples

fluid generate transformation
fluid generate transformation contract.fluid.yaml -o ./dbt_project
fluid generate transformation contract.fluid.yaml -o ./dbt_project --dbt-validate
fluid generate schedule contract.fluid.yaml --scheduler airflow -o dags
fluid generate ci --system github
fluid generate standard contract.fluid.yaml --format odps
fluid generate standard contract.fluid.yaml --format odps-v4.1

Compatibility note

fluid generate-airflow still works for Airflow generation, but current docs lead with fluid generate schedule --scheduler airflow.