Forum Discussion

lavginqo2's avatar
lavginqo2
Frequent Visitor
3 days ago
Solved

Approach for automating Dataflow Gen2 connection binding across Dev/Prod?

We're deploying Dataflow Gen2 from Dev to Prod via fabric-cicd with all destination Lakehouse IDs and source parameters fully parameterized. Definitions deploy cleanly. The blocker: every query's da...
data engineering
  • lavginqo2's avatar
    lavginqo2
    2 days ago

    Thanks — this is useful, particularly the definition APIs. One clarification: source connection rebinding is already solved on our side.

    It is working now as there was something else that I missed.

    Thanks !

Kagiyama_yutaka's avatar
Kagiyama_yutaka
Icon for Continued Contributor rankContinued Contributor
3 days ago

Dataflow Gen2 keeps the connection tied to the workspace, and CI/CD doesn’t move it, and there’s no REST or SPN way to rebind it after a deploy.

Just make the same connection in Prod ahead of time, push the flow, open each query and pick that Prod connection yourself. For bigger flows people usually split the dataflow so the reconnect work stays manageable.