Deployement Pipeline support for Dataflow Gen2

[chandulae]

Hi,

We are experiencing significant issues with deploying Dataflow Gen 2 from development to production.

Currently, we are using the manual export and import method, saving them to a local drive.

Handling over 100 tables makes this manual method very time-consuming.

Could we have support for a deployment pipeline with Dataflow Gen 2? If it is already planned, could we know the release date?

Thank you.

[fbcideas_migusr]

I am surprised that this is not on the Fabric roadmap. Would be nice to know when Microsoft plans to fix this issue.

[Nick_Hilton]

This is essential for actually moving between dev, test and production. Please can we get this on the release timeline.

[anthonyl1]

This feature is preventing us from migrating to Fabric

[omer_aytac]

This missing features is stopping us from using Dataflow Gen2 in production. Can we get a release date?

[fbcideas_migusr]

This is supposed to be available now as of 20/11/24. It was published on the blog: https://learn.microsoft.com/en-us/fabric/data-factory/dataflow-gen2-cicd-and-git-integration

[anon97242]

Deployment pipelines should allow for rules in the different environment/stages for DataflowGen2 CICD items.

Ideally specifying differenent (paramaterized) sources and destinations in each stage, for each DataflowGen2 CICD item.

[JoelGagnon]

how can this not being available? I had to trash my Datamart and now we regress again.

[TBNPieter]

Hi Microsoft, How does this idea need extra votes? When it should be a basic functionality and is part of your CI/CD Best Practices. CI/CD is a best practice but we can't use the new Dataflow Gen 2 (with CI/CD) in a deployment pipeline to automate our CI/CD-deployments??? So with every deployment (dev to test or production), we have to manually change the source and destination of every Dataflow? This should already be on the roadmap in my opinion. For us, It is holding back our entire organization Fabric setup because we mainly use Dataflows and we wanted to start implementing the CI/CD-approach. Kind regards, I am really hoping that this issue gets sorted out quickly.