fabric-deployment-pipelineslisted

Use for Fabric / Power BI service-side deployment pipelines — the workspace-is-source-of-truth ALM surface promoting content stage to stage (dev → test → prod) via the Core REST API `/v1/deploymentPipelines` or `fab api`. Covers pipeline/stage lifecycle (2–10 stages, permanent once created), workspace assign/unassign, Deploy Stage Content as an LRO (202 + `x-ms-operation-id`, 300-item cap), per-operation delegated scopes (`Pipeline.Read.All`/`Pipeline.ReadWrite.All`, `Workspace.ReadWrite.All` to assign, `Pipeline.Deploy` — its own scope — to deploy), the two-permission model of pipeline Admin plus a workspace role on both stages, item pairing and its folder tie-breaker, autobinding across pipelines, portal-only deployment rules, and the limits that bite: PBIR reports unsupported, backward deploys empty-target and full-only, Direct Lake not rebinding, unassign destroying history and rules. For Git-driven deploys use fabric-cicd or `fab deploy`; for Data Factory orchestration items, fabric-data-pipeline.
wardawgmalvicious/agent-config · ★ 1 · AI & Automation · score 77

Install: claude install-skill wardawgmalvicious/agent-config

# Fabric deployment pipelines (service-side) The **service-side** ALM surface: a pipeline of ordered stages, each holding one workspace, promoting content from one stage to the next. The **workspace is the source of truth** — no local code, no repository. Driven from the portal, or from the Fabric Core REST API under `https://api.fabric.microsoft.com/v1/deploymentPipelines`. ## Which surface am I on? Three different things deploy Fabric content. Pick first — getting this wrong invalidates everything after it. | Surface | Source of truth | Use when | |---|---|---| | **Deployment pipelines** (this skill) | The **workspace** | Promoting a dev workspace to test/prod inside the service; stage-to-stage, nothing on disk | | `fabric-cicd` (Python library) | **Git** | Scripted deploys from a repo checkout; `publish_all_items`, `parameter.yml` | | `fab deploy --config` | **Git** | One-command CLI wrapper over the same library | **Don't mix Git-driven deploys and service-side pipelines on the same workspaces.** Decision guide: [Choose the best Fabric CI/CD workflow](https://learn.microsoft.com/fabric/cicd/manage-deployment). ## Concepts - A pipeline has **2 to 10 stages** (default 3). **The number of stages and their names are permanent** once the pipeline is created — only a stage's *public* flag can change afterwards. - Each stage holds **at most one workspace**, and a workspace can be assigned to **at most one** pipeline stage, tenant-wide. - Deploys run between **adjace