Fluid Forge
Why Forge
Concepts
Get Started
  • Consume a Data Product
  • See it run
  • Demos
  • Local (DuckDB)
  • Source-Aligned (Postgres → DuckDB)
  • AI Forge + Data Models
  • MCP Output Port — Serve to AI Agents
  • GCP (BigQuery)
  • Snowflake Team Collaboration
  • Declarative Airflow
  • Orchestration Export
  • Jenkins CI/CD
  • Universal Pipeline
  • 11-Stage Production Pipeline
  • Catalog Forge End-to-End
CLI Reference
  • Agent Policy (concept)
  • MCP Output Port — Serve to Agents
  • MCP deep-dive
  • AI-assisted authoring
  • LLM providers & backends
  • Overview
  • Quickstart
  • Examples
  • Your own CI
  • Your own scaffolding
  • Custom validator
  • Apply hook
  • Reference
  • Overview
  • Architecture
  • GCP (BigQuery)
  • AWS (S3 + Athena)
  • Snowflake
  • Local (DuckDB)
  • Custom Providers
  • Roadmap
GitHub
Why Forge
Concepts
Get Started
  • Consume a Data Product
  • See it run
  • Demos
  • Local (DuckDB)
  • Source-Aligned (Postgres → DuckDB)
  • AI Forge + Data Models
  • MCP Output Port — Serve to AI Agents
  • GCP (BigQuery)
  • Snowflake Team Collaboration
  • Declarative Airflow
  • Orchestration Export
  • Jenkins CI/CD
  • Universal Pipeline
  • 11-Stage Production Pipeline
  • Catalog Forge End-to-End
CLI Reference
  • Agent Policy (concept)
  • MCP Output Port — Serve to Agents
  • MCP deep-dive
  • AI-assisted authoring
  • LLM providers & backends
  • Overview
  • Quickstart
  • Examples
  • Your own CI
  • Your own scaffolding
  • Custom validator
  • Apply hook
  • Reference
  • Overview
  • Architecture
  • GCP (BigQuery)
  • AWS (S3 + Athena)
  • Snowflake
  • Local (DuckDB)
  • Custom Providers
  • Roadmap
GitHub
  • Introduction

    • Home
    • Why Fluid Forge
    • Getting Started
    • Snowflake Quickstart
    • See it run
    • Forge Data Model
    • Vision & Roadmap
    • Playground
    • FAQ
  • Concepts

    • Concepts
    • Builds, Exposes, Bindings
    • What is a contract?
    • Quality, SLAs & Lineage
    • Governance & Policy
    • Agent Policy (LLM/AI governance)
    • Providers vs Platforms
    • Fluid Forge vs alternatives
  • Data Products

    • Consume a Data Product
    • Product Types — SDP, ADP, CDP
  • Walkthroughs

    • Walkthrough: Local Development
    • Source-Aligned: Postgres → DuckDB → Parquet
    • AI Forge And Data-Model Journeys
    • Walkthrough: MCP Output Port
    • 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
    • The 11-Stage Pipeline
    • End-to-End Walkthrough: Catalog → Contract → Transformation
  • CLI Reference

    • CLI Reference
    • Core workflow

      • fluid init
      • fluid demo
      • fluid forge
      • fluid validate
      • fluid plan
      • fluid apply
      • fluid diff
      • fluid status
    • Build & ship

      • fluid bundle
      • fluid generate
      • fluid generate artifacts
      • fluid validate-artifacts
      • fluid verify-signature
      • fluid generate iac
      • fluid generate-airflow
      • fluid generate-pipeline
      • fluid viz-graph
      • fluid publish
      • fluid ship
      • fluid rollback
      • fluid schedule-sync
    • AI & Agents

      • fluid ai
      • fluid agents
      • fluid mcp
      • fluid memory
      • fluid stats
      • fluid skills
    • Quality & governance

      • fluid test
      • fluid verify
      • fluid contract-tests
      • fluid contract-validation
      • fluid policy
      • fluid policy check
      • fluid policy compile
      • fluid policy apply
    • Standards & interoperability

      • fluid odps
      • fluid odps-bitol
      • fluid odcs
      • fluid export
      • fluid export-odps
      • fluid exporters
      • fluid import
      • fluid market
      • fluid datamesh-manager
    • Project & workspace

      • fluid product-new
      • fluid product-add
      • fluid workspace
      • fluid contract
      • fluid split
      • fluid config
      • fluid providers
      • fluid plugins
      • fluid provider-init
      • fluid auth
      • fluid secrets
      • fluid ide
      • fluid scaffold-ci
      • fluid scaffold-composer
      • fluid scaffold-ide
      • fluid docs
      • fluid runs
      • fluid retention
      • fluid describe
      • fluid doctor
      • fluid roadmap
      • fluid version
    • Catalog adapters

      • Source Catalog Integration (V1.5)
      • Publishing to a Catalog — Overview
      • BigQuery Catalog
      • Snowflake Horizon Catalog
      • Databricks Unity Catalog
      • Google Dataplex Catalog
      • AWS Glue Data Catalog
      • DataHub Catalog
      • Data Mesh Manager Catalog
      • OpenMetadata Catalog
    • CLI by task

      • CLI by task
      • Add quality rules
      • Add agent governance
      • Debug a failed pipeline run
      • Switch clouds with one line
  • Recipes

    • Recipes
    • Recipe — add a quality rule
    • Recipe — switch clouds with one line
    • Recipe — tag PII in your schema
    • Write a contract that consumes another contract
    • Generate per-environment overlays
  • SDK & Plugins

    • SDK & Plugins
    • Quickstart — your first plugin
    • Examples

      • Runnable examples
      • Example: hello-scaffold — the minimal viable plugin
      • Example: gitlab-ci-scaffold — generate a complete CI project
      • Example: steward-validator — a custom governance rule
      • Example: prod-key-guard — apply-time invariant check
    • Journeys

      • Journeys
      • Your own CI/CD

        • You have your own CI/CD setup, no problem
        • GitLab CI — the bundle template
        • GitHub Actions — the bundle template
        • Jenkins — the bundle template
        • CircleCI — the bundle template
      • You have a strict project layout, no problem
      • You have governance rules, no problem
      • You want a check at apply time, no problem
    • Reference

      • Reference
      • Roles reference
      • Entry points reference
      • Trust model
      • Packaging
      • Companion packages
  • Providers

    • Providers
    • Provider Architecture
    • GCP Provider
    • AWS Provider
    • Snowflake Provider
    • Local Provider
    • Creating Custom Providers
    • Provider Roadmap
  • AI & Agents

    • MCP Server
    • Built-in And Custom Forge Guidance
    • Forge Discovery Guide
    • Forge Memory Guide
    • Authoring Forge Tools
    • Guided fluid forge UX
    • LLM Providers
    • LiteLLM Backend
    • Capability Warnings
    • Cost Tracking
    • FLUID Forge Contract GPT Packet
    • Agentic Primitives
  • Operate & Deploy

    • Airflow Integration
    • Blueprints
    • Source-Aligned Acquisition
  • Govern & Secure

    • Governance, Compliance & the Business Case
    • Governance & Compliance
    • Network Safety
    • Credential Resolver — Security Model
  • Configuration & Reference

    • Environment Variables
    • Typed Errors
    • Typed CLI Errors
    • API Stability — fluid_build.api
  • Architecture & Releases

    • V1.5 Catalog Integration — Architecture Deep-Dive
    • V1.5 + V2 Hardening — Release Notes
  • Project

    • Contributing to Fluid Forge
    • Fluid Forge Docs Baseline: CLI 0.9.0
    • Fluid Forge Docs Baseline: CLI 0.8.11
    • Fluid Forge Docs Baseline: CLI 0.8.10
    • Fluid Forge Docs Baseline: CLI 0.8.9
    • Fluid Forge Docs Baseline: CLI 0.8.8
    • Fluid Forge Docs Baseline: CLI 0.8.7
    • Fluid Forge Docs Baseline: CLI 0.8.6
    • Fluid Forge Docs Baseline: CLI 0.8.5
    • Fluid Forge Docs Baseline: CLI 0.8.4
    • Fluid Forge Docs Baseline: CLI 0.8.3
    • Fluid Forge Docs Baseline: CLI 0.8.0
    • Fluid Forge Docs Baseline: CLI 0.7.11
    • Fluid Forge Docs Baseline: CLI 0.7.9
    • Fluid Forge v0.7.1 - Multi-Provider Export Release

Fluid Forge Docs Baseline: CLI 0.8.8

Release Date: May 31, 2026 Status: Superseded by 0.8.9 (supersedes 0.8.7)

Headline

0.8.8 delivers two headline improvements: an on-demand OpenTofu provisioner — fluid apply --ensure-opentofu downloads a pinned, SHA-256-verified tofu using only the Python standard library (no root, gpg, cosign, curl, or unzip), so cloud applies finally run on locked-down / non-root CI runners (a non-root Jenkins agent is the canonical case); and a real fluid market — catalog discovery now runs over MCP against DataHub, OpenMetadata, and Data Mesh Manager (replacing the previous demo data), with two-phase metadata enrichment and offline blueprints. No schema change vs 0.8.7 (contract schema stays at fluidVersion 0.7.4).

Who should upgrade

Anyone running fluid apply against AWS / GCP / Snowflake from CI — especially non-root runners that previously failed with opentofu_engine_no_tofu. Also anyone using fluid market against a real DataHub / OpenMetadata / Data Mesh Manager catalog.

What changed in v0.8.8

Added

  • On-demand OpenTofu provisioner — fluid apply --ensure-opentofu. Cloud applies (AWS / GCP / Snowflake) run through the OpenTofu engine, which shells out to tofu. The official standalone installer needs root (/usr/local/bin) and gpg/cosign to verify — which a non-root CI agent can't provide, so generated cloud-apply pipelines failed on a fresh runner with opentofu_engine_no_tofu. When --ensure-opentofu is set and tofu is missing, FLUID downloads the pinned OpenTofu release zip + its SHA256SUMS over TLS, verifies the SHA-256 before extracting, extracts only the tofu entry (no zip-slip), installs it to a writable dir (the console-scripts dir, else ~/.cache/fluid), and prepends it to the process PATH. It uses only the Python standard library — no root, gpg, cosign, curl, or unzip — and is idempotent (a usable tofu at/above the engine's version floor is left untouched, so a pre-baked runner image still wins). Override the pinned version with FLUID_OPENTOFU_VERSION.

    # provision tofu on demand if it's missing, then apply
    fluid apply runtime/plan.json --ensure-opentofu --yes
    

    fluid generate ci bakes --ensure-opentofu into the apply stage of all seven CI runners (Jenkins, GitHub Actions, GitLab, Azure DevOps, Bitbucket, CircleCI, Tekton). The flag is idempotent and a no-op for native / local applies that never touch the OpenTofu engine.

  • fluid market real catalog discovery over MCP — DataHub, OpenMetadata, and Data Mesh Manager, replacing the previous demo data.

  • fluid market metadata enrichment — a two-phase fetch surfaces full product detail plus data-asset column schema; --detailed is now a true superset of the listing rather than a replacement.

  • fluid market onboarding + trust/usage surfacing — actionable next steps and trust / usage signals in the listing.

  • fluid market --blueprints works offline via bundled blueprints.

Changed

  • fluid market no longer serves fabricated demo data for roadmap-only catalog connectors (datahub / glue / data-catalog / rest); they are skipped with a clear roadmap note.
  • fluid market --format json emits clean, machine-parseable output.
  • Faster CLI startup — validation providers are lazy-loaded.

Fixed

  • Generated dev-source Jenkins pipelines could not call fluid. The dev-source bootstrap ran pip uninstall -y data-product-forge — deleting the fluid console script (the package's entry point) — then invoked fluid relying only on PYTHONPATH, so stage 0 died with fluid: not found. The bootstrap now keeps the installed console script (a PYTHONPATH prepend already shadows its modules with the bind-mounted checkout) and sanity-checks the import.
  • Generated Jenkins policy-apply stage emitted an empty --mode on the first build (before the param is injected), which fluid policy-apply rejected; it now defaults to enforce.
  • fluid forge --from-source sanitizes the contract id derived from a sqlite file path.
  • build-runners now warn when an inline-SQL build declares engine: dbt (previously silently ignored).
  • fluid policy-apply surfaces a no-op message when a provider has no policy applier instead of appearing to succeed silently.
  • fluid market per-catalog MCP search-limit param corrected (OpenMetadata size, DataHub num_results), and the command raises a proper error instead of crashing with a TypeError.

Removed

  • Dead, never-wired-in modules: fluid_build/validation.py and the unused SQL-allowlist helpers (parse_and_allowlist_sql + type/language validators).

Security

  • Re-symmetrized the Snowflake provider-local secret redactor with the global logging filter so new secret shapes are masked in both layers.

Upgrade

pip install --upgrade "data-product-forge==0.8.8"

Contracts need no changes — contract schema stays at fluidVersion 0.7.4, unchanged from 0.8.7.

Edit this page on GitHub
Last Updated: 6/1/26, 2:32 PM
Contributors: fas89, Claude Opus 4.8
Prev
Fluid Forge Docs Baseline: CLI 0.8.9
Next
Fluid Forge Docs Baseline: CLI 0.8.7