Shared Deployed Pipelines

Definition

A shared deployed pipeline is a pipeline that multiple workspaces reference and use. This means:

• One Deployed Pipeline, Many Workspaces: All workspaces share the same underlying pipeline and processed data.

• Independent Drafts – Each workspace maintains its own draft version of the pipeline, allowing independent experimentation without affecting the shared deployed pipeline until deployment.

• Immediate Data Access: Processed data is accessible to development workspaces without needing to re-deploy or re-stream data, providing instant access to semantic layer artifacts like Runtime Fields and KPIs in your development workspaces without delays.

Creating a Shared Deployed Pipeline

Shared deployed pipelines are automatically created when you copy a workspace that contains a deployed pipeline. This means:

• The original and copied workspace will share the same deployed pipeline and its data.

• Each workspace retains an independent draft of the pipeline.

• Subsequent copies of either workspace will continue referencing the same shared deployed pipeline.

  
  

Running / Pausing a Shared Deployed Pipeline

• ⚠️ Starting or pausing a shared deployed pipeline affects all workspaces using it ⚠️ 

• Pipeline status changes are immediately reflected in all referencing workspaces.

• When attempting to run or pause a shared deployed pipeline, a warning modal will appear, listing all affected workspaces. 

  • The Production workspace is highlighted in bold.

  • 
    
  • 
    

Removing a Shared Deployed Pipeline

• Removing a shared deployed pipeline from a workspace only removes its reference in that workspace; other workspaces remain unaffected.

• If at least one workspace still references the pipeline, it remains active.

• When the last workspace removes its reference, the pipeline and its data are permanently deleted.

Unsharing a Pipeline

• Redeploying a pipeline removes the shared reference, creating a new, separate deployed pipeline.

• Other workspaces still referencing the original shared deployed pipeline remain unaffected.

Archiving a Workspace with a Shared Deployed Pipeline

• Archiving a workspace makes the shared deployed pipeline unavailable for that workspace only.

• Other workspaces referencing the pipeline remain unaffected.

• If no other workspaces reference the pipeline, the pipeline and its data are fully removed.