Current Pain Point
Currently, when using Variable Libraries in Fabric pipelines, each variable must be manually added one-by-one to a pipeline before it can be referenced. This creates significant friction, especially when:
- Working with libraries containing dozens of variables
- Adding new variables to an existing library (requires updating every pipeline that needs them)
- Managing multiple environments with different configurations
Proposed Solution
Allow dynamic access to Variable Library variables without pre-registering them in each pipeline. Two implementation options:
Option A: Link Entire Variable Library
- Add capability to link a full Variable Library to a pipeline
- All variables in that library become immediately accessible
Option B: Dynamic Expression Function
@GetVariable('VariableLibraryName', 'VariableName')- Reference any variable from any Variable Library in the workspace dynamically
- No pre-registration required
- Enables truly parameterized, reusable pipelines
Benefits
Benefit Impact
| Maintainability | Add variables once to the library, use everywhere instantly |
| Reduced Errors | No more forgetting to add variables to pipelines |
| DRY Principle | Single source of truth for configuration values |
| CI/CD Friendly | Easier to manage environment-specific configs across deployments |
| Developer Experience | Faster pipeline development, less repetitive clicking |
Use Case Example
Imagine a data platform with 50+ pipelines all needing access to common configuration values (connection strings, retention days, environment flags). Today, adding one new variable means manually updating all 50 pipelines. With dynamic access, you update the library once and you're done.
No CommentsBe the first to comment
