I have three workspaces -- DEV, UAT, and Prod. Within these workspaces, I have several independent projects - each with their own deployment schedule and processes.
The current pipeline process makes it nearly impossible to deploy these projects independently of one another because a human being has to rebuild the pipeline for every deployment. Not only that, but the difficulty in rebinding notebooks, semantic models, etc as part of the deployment makes the whole pipeline process a non-starter.
It would make the deployment pipeline process much easier/better if I could:
1) specify what data pipelines, data flows, notebooks, semantic models, reports, environments, and lakehouses need to move between workspaces
2) specify what data within lakehouses needs to be copied
3) rebind any notebooks, semantic models, and reports
In short, I want a pipeline package for each project that I can define within the source workspace(s)
NaamaTsafrir
on:
Domain specific Tags
on:
Auto-Spacing Option Between Visuals When Aligning ...
on:
In "Manage relationships" view I need to filter by...
ToddChitt
on:
The list of available connections via a pipeline C...