Providers

Fluid Forge uses one contract format across local and provider-backed execution targets.

Docs baseline

CLI release covered by the primary docs: 0.7.9
Current scaffolded contract examples: fluidVersion: 0.7.2

Some deep-dive provider pages still preserve older 0.7.1 snippets for backward-compatibility context. Those examples should not be read as “current version” guidance.

Provider overview

Provider	Plan / Apply	Scheduling docs stance	Status
GCP	Yes	Prefer `fluid generate schedule`	Production
AWS	Yes	Prefer `fluid generate schedule`	Production
Snowflake	Yes	Prefer `fluid generate schedule`	Production
Local	Yes	Local-first onboarding	Production

Compatibility note: fluid generate-airflow still exists, but the primary docs path is fluid generate schedule --scheduler airflow.

Quick start by provider

GCP

gcloud auth application-default login
gcloud config set project YOUR_PROJECT_ID
fluid apply contract.fluid.yaml --provider gcp --yes

AWS

aws configure
fluid apply contract.fluid.yaml --provider aws --yes

Snowflake

export SNOWFLAKE_ACCOUNT=your_account
export SNOWFLAKE_USER=your_user
fluid apply contract.fluid.yaml --provider snowflake --yes

Local

fluid init my-project --quickstart
cd my-project
fluid apply contract.fluid.yaml --yes

Beyond the apply-capable providers above, Fluid Forge can export contracts to public data-product standards and publish them to catalogs. Both surfaces live inside existing CLI commands rather than as separate provider pages.

Export formats — `fluid generate standard`

Format	What it is	Reference
OPDS	Open Data Product Specification JSON v1.0	`generate standard`
ODCS	Open Data Contract Standard v3.1.0 (Bitol.io)	`generate standard`
ODPS	Open Data Product Standard — Bitol variant, input-port lineage	`generate standard`
ODPS-Bitol	ODPS in strict-conformance mode	`generate standard`

Shortcut: fluid export-opds contract.fluid.yaml — equivalent to fluid generate standard --format opds.

Publishing — `fluid publish`

Catalog	Reference
FLUID Command Center	`fluid publish`
Data Mesh Manager / Entropy Data	`fluid publish` → DMM section

Notes

Use provider-specific guides when you need deep target details.
Use CLI Reference for command syntax.
Use Getting Started for the local-first workflow.

Need a hand with a specific provider? Start a discussion or open an issue.