Forum Discussion

krisjones's avatar
krisjones
Icon for Helper I rankHelper I
1 year ago
Solved

Deployment Pipeline fails when deploying a data pipeline

I cannot deploy a Fabric Data Pipeline resource from one workspace to another using Fabric Deployment Pipelines trigger by REST API calls. When I do it manually it works fine.  When I deploy other ...
admin
cicd
workspaces
  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi krisjones ,

    Thanks for posting in Microsoft Fabric Community and for sharing the details.

    Based on the available information and testing, it appears that while Data Pipelines are supported in Fabric Deployment Pipelines through the UI, there may be limitations when using the Deployment Pipelines REST API to deploy Data Pipelines between workspaces.

    This observation is aligned with the current state of the APIs--while the Data Pipeline REST API supports managing Data Pipelines for CI/CD scenarios, integrating this with the Deployment Pipelines REST API for workspace-to-workspace promotion might not be fully supported yet.

     

    Additional Suggestions:

    1. Check the following resources to ensure all configurations align with best practices and required permissions:

    2. If the issue persists, consider using the Data Pipeline REST API directly for deployment automation.

    If needed, raising a support ticket with Microsoft, providing the full API response and request details, might help clarify the current limitations and available workarounds.

     

    Hope this helps. Please reach out for further assistance.
    If this post helps, then please consider to give a kudos and Accept as the solution to help the other members find it more quickly.


    Thank you.

garddolau's avatar
garddolau
Icon for Advocate IV rankAdvocate IV
1 year ago

Can anyone for MS confirm there is currently a known limitation/issue for this combination please?

(a) Deployment Pipelines REST API = https://api.fabric.microsoft.com/v1/deploymentPipelines/{{deployment_pipeline_id}}/deploy

 

(b) itemType = DataPipeline

 

(c) via Service Principal

 

(d) Service Principal has admin access on all 3 workpsaces inlcude in the deployment pipeline

 

(e) Service Principal has admin access on the deployment pipeline

 

(f) Method being used to post to the API works fine other item types eg(Lakehouse, VariableLibrary, SemanticModel, Notebook)

 

(g) When completing the test I am only trying 1 DataPipeline

 

(h) When completing the test the Data Pipeline being used to test is empty so has no dependencies

 

  • Anonymous's avatar
    Anonymous
    Not applicable
    1 year ago

    Hi garddolau ,
    Thanks for checking on this.
    At the moment, there’s no official documentation confirming this as a known issue, but the behavior you’re seeing is consistent with other recent reports.

    As noted, the recommendation from Microsoft Support in this case was to avoid using Deployment Pipelines for Data Pipelines and instead implement automation using REST APIs to export and recreate pipelines across workspaces.

    This REST-based approach appears to be working reliably and may be the best workaround until more formal guidance or fixes are provided.

    Since a support ticket has already been raised by krisjones and the matter is under discussion with Microsoft Support, it would be best to wait for the outcome of that investigation.

    However, if this is blocking a critical scenario on your end, raising a separate support ticket would help ensure it receives the appropriate attention for your specific context.

    If any updates or confirmations become available, it would be helpful to share them here for the benefit of others facing similar challenges.

     

    Hope this helps. Please reach out for further assistance.

    Thank you.