fabric-data-pipelinelisted
Install: claude install-skill wardawgmalvicious/agent-config
# Fabric Data Pipeline definitions
Covers the **Git-serialized** form of a DataPipeline item — the JSON an
agent edits when there is no portal to validate against.
**Not here, deliberately:** expression syntax (`@concat`, `coalesce`,
the ForEach variable race) belongs to the `coding-expressions` rule,
which globs the same file and always co-loads. Connection rebinding
across environments belongs to `fabric-cicd`. The `libraryVariables`
block's own mechanics belong to `fabric-variable-library`. Copy activity
source/sink/dataset internals are not covered at all.
## 1. What Git holds
| File | Required | What it is |
| --- | --- | --- |
| `pipeline-content.json` | yes | The pipeline: activities, parameters, variables |
| `.platform` | no | Item metadata — `displayName`, `logicalId` |
| `.schedules` | no | Job-scheduler triggers, one file per item |
Serialization mechanics (EOF newlines, CRLF/LF, `.gitattributes`) are in
the `fabric-git-serialization` rule, which globs this folder too.
## 2. The definition envelope
```json
{ "properties": {
"activities": [ ... ],
"parameters": { "DryRun": { "type": "bool", "defaultValue": false } },
"variables": { "ChangedEntities": { "type": "Array", "defaultValue": [] } },
"libraryVariables": { "EnvSuffix": { "type": "String",
"variableName": "EnvironmentSuffix", "libraryName": "MyVarLib" } }
} }
```
**The REST schema page documents only `activities` and `description`.**
Every real pipeline also carri