Fluid ForgeFluid Forge
Home
Get Started
  • Local (DuckDB)
  • GCP (BigQuery)
  • Snowflake Team Collaboration
  • Declarative Airflow
  • Orchestration Export
  • Jenkins CI/CD
  • Universal Pipeline
CLI Reference
  • Overview
  • Architecture
  • GCP (BigQuery)
  • AWS (S3 + Athena)
  • Snowflake
  • Local (DuckDB)
  • Custom Providers
  • Roadmap
GitHub
GitHub
Home
Get Started
  • Local (DuckDB)
  • GCP (BigQuery)
  • Snowflake Team Collaboration
  • Declarative Airflow
  • Orchestration Export
  • Jenkins CI/CD
  • Universal Pipeline
CLI Reference
  • Overview
  • Architecture
  • GCP (BigQuery)
  • AWS (S3 + Athena)
  • Snowflake
  • Local (DuckDB)
  • Custom Providers
  • Roadmap
GitHub
GitHub
  • Introduction

    • /
    • Getting Started
    • Snowflake Quickstart
    • Vision & Roadmap
  • Walkthroughs

    • Walkthrough: Local Development
    • Walkthrough: Deploy to Google Cloud Platform
    • Walkthrough: Snowflake Team Collaboration
    • Declarative Airflow DAG Generation - The FLUID Way
    • Generating Orchestration Code from Contracts
    • Jenkins CI/CD for FLUID Data Products
    • Universal Pipeline
  • CLI Reference

    • CLI Reference
    • init Command
    • validate Command
    • plan Command
    • apply Command
    • verify Command
    • generate-airflow Command
  • Providers

    • Providers
    • Provider Architecture
    • GCP Provider
    • AWS Provider
    • Snowflake Provider
    • Local Provider
    • Creating Custom Providers
    • Provider Roadmap
  • Advanced

    • Blueprints
    • Governance & Compliance
    • Airflow Integration
    • Built-in And Custom Forge Agents
    • FLUID Forge Contract GPT Packet
    • Forge Copilot Discovery Guide
    • Forge Copilot Memory Guide
  • Project

    • Contributing to Fluid Forge
    • Fluid Forge v0.7.1 - Multi-Provider Export Release

apply Command

Execute a FLUID contract: load data, run transformations, create infrastructure.

Syntax

fluid apply <contract-file> [options]

The <contract-file> can be a .fluid.yaml contract or a previously saved plan JSON file.

Options

Execution Control

OptionDescriptionDefault
--yesSkip confirmation promptfalse
--dry-runShow what would happen without executingfalse
--timeout <minutes>Global timeout120
--parallel-phasesEnable parallel phase executionfalse
--max-workers <n>Maximum parallel workers4

Safety & Rollback

OptionDescriptionDefault
--rollback-strategynone, immediate, phase_complete, full_rollbackphase_complete
--require-approvalRequire approval for destructive operationsfalse
--backup-stateCreate a state backup before executionfalse
--validate-dependenciesValidate all dependencies before executionfalse

Reporting & Monitoring

OptionDescriptionDefault
--report <path>Report output pathruntime/apply_report.html
--report-formathtml, json, markdownhtml
--metrics-exportnone, prometheus, datadog, cloudwatchnone
--notify <dest>Notification destinations—

Development & Debugging

OptionDescriptionDefault
--verboseVerbose outputfalse
--debugDebug-level loggingfalse
--keep-temp-filesKeep temporary files after executionfalse
--profileEnable performance profilingfalse

Advanced

OptionDescriptionDefault
--workspace-dir <path>Working directory.
--state-file <path>Custom state file location—
--config-override <json>JSON configuration override string—
--provider-config <path>Path to provider configuration file—

What It Does

The apply command orchestrates a multi-phase execution:

  1. Validate — checks contract syntax and provider configuration
  2. Plan — generates the execution plan
  3. Execute — runs each phase (create resources, load data, run transforms)
  4. Report — generates an execution report

Examples

Local Execution

# Quick local run
fluid apply contract.fluid.yaml --yes

Cloud Deployment

# Deploy to GCP
fluid apply contract.fluid.yaml --provider gcp --env prod

Preview Without Executing

fluid apply contract.fluid.yaml --dry-run

Shows the full execution plan without making any changes.

Production-Safe Deployment

fluid apply contract.fluid.yaml \
  --require-approval \
  --backup-state \
  --rollback-strategy full_rollback \
  --report-format json \
  --notify slack://data-team

CI/CD Pipeline

fluid validate contract.fluid.yaml --strict && \
fluid apply contract.fluid.yaml --yes --report-format json

Parallel Execution

fluid apply contract.fluid.yaml \
  --parallel-phases \
  --max-workers 8 \
  --timeout 60

Rollback Strategies

StrategyBehavior
noneNo rollback on failure
immediateRoll back the failing phase immediately
phase_completeLet the current phase finish, then roll back
full_rollbackRoll back all completed phases

See Also

  • plan command — preview changes before applying
  • verify command — verify deployment matches contract
  • Getting Started Guide — end-to-end walkthrough
Edit this page on GitHub
Last Updated: 3/12/26, 1:03 PM
Contributors: khanya_ai
Prev
plan Command
Next
verify Command