Forum Discussion

SanderTK's avatar
SanderTK
Icon for Advocate II rankAdvocate II
7 months ago
Solved

Deployment Pipeline compare using Fabric REST API

Hi all,   I am working with significant number of workspaces that each operate using deployment pipelines.  The goal is to build a notebook that runs every evening to check for changes in the pipe...
data engineering
  • v-karpurapud's avatar
    v-karpurapud
    7 months ago

    Hi SanderTK 

    You don’t need the complete UI comparison logic. If an artifact in DEV has a modified time that’s later than its last deployment time in the pipeline, it means there are changes in DEV that haven’t been deployed yet. This is enough to identify possible missed deployments.While it won’t show the specific changes, it effectively addresses the issue of missed deployments without adding unnecessary complexity.


    If you have any further questions, feel free to reach out and we'll be glad to assist.

     

    Regards,

    Microsoft Fabric Community Support Team.
     

SanderTK's avatar
SanderTK
Icon for Advocate II rankAdvocate II
7 months ago

What I mean with this is that fixes often get implemented in DEV without then being deployed to PROD. People simply forget to deploy their own fixes, features, etc.

I know it sounds a bit ridiculous but it is the current situation.

v-karpurapud's avatar
v-karpurapud
Icon for Community Support rankCommunity Support
7 months ago

Hi SanderTK 

You don’t need the complete UI comparison logic. If an artifact in DEV has a modified time that’s later than its last deployment time in the pipeline, it means there are changes in DEV that haven’t been deployed yet. This is enough to identify possible missed deployments.While it won’t show the specific changes, it effectively addresses the issue of missed deployments without adding unnecessary complexity.


If you have any further questions, feel free to reach out and we'll be glad to assist.

 

Regards,

Microsoft Fabric Community Support Team.