Forum Discussion

Matthew_G's avatar
Matthew_G
Icon for Advocate I rankAdvocate I
2 years ago
Solved

Dynamic pipelines to use across workspaces

Hi fellow Fabricators,   The set-up: Currently you can't use a deployment pipleline to deploy data pipelines. We have three different workspaces, basically dev, test, prod - we did it this way to ...
pipelines
  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi Matthew_G 
    Thanks for using Fabric Community.
    You need to select the "Add dynamic content" option within the drop down and pass in the GUID.

     


    You need to create a new parameter for the stored procedure activity.
    The parameter value should be Lakehouse/Data Warehouse/KQL Database object ID. To get your Lakehouse/Data Warehouse/KQL Database object ID, open your Lakehouse/Data Warehouse/KQL Database in your workspace, and the ID is after /lakehouses/or /datawarehouses/ or /databases/ in your URL.

     

     


    Please refer to this link for more information: Link1
    Hope this helps. Please let me know if you have any further questions.

  • Matthew_G's avatar
    Matthew_G
    2 years ago

    Thanks, it looks a bit different for the Stored Procedure Activity.

    When you add dynamic content to the Warehouse it then also requests a SQL connection string.

    I then added two parameters, the connection string and the warehouse guid, adding it as dynamic content.

    This now works.

     

     

     

     

JerryPan's avatar
JerryPan
Regular Visitor
2 years ago

Matthew_G , Anonymous ,

I have added the same parameters as Warehouse ID, SQL connection string and use them in Stored Procedure Activity. It works well in current Dev workspace. But when I use release pipeline deploy it to next stage workspace (UAT), the parameters are still pointing to Dev workspace warehouse. How can we change these parameters during deployment?

 

Thanks

 

jerry

 

Matthew_G's avatar
Matthew_G
Icon for Advocate I rankAdvocate I
2 years ago

Hi Jerry, yeah, you will need to change the parameters in each pipeline though each time you deploy they will be overwritten. Unfortunately even in the deployment pipeline you can't set the parameters. What you could do is have two pipelines in each workspace where pipeline 1 kicks off pipeline 2 and passess the parameters. That way when you deploy changes you can just deploy pipeline 2 and it shouldnt break anything. I'm sure there is a better solution out there.