Related to this question someone else recently posted, I have a similar need/use case: https://community.fabric.microsoft.com/t5/Data-Pipeline/dynamic-library-variables/m-p/4663725/highli...
I am currently using a config table in a warehouse to run pipelines for things like chained refreshes on dependency, and also automatically creating shortcuts to end-user lakehouses to various gold-layer warehouses, depending on which warehouses they have been approved for access to, which is partially captured in the config table.
Right now, some of the pipeline processing and API steps could be streamlined and simplified by supplying more directly things like workspace/warehouse/lakehouse ids per environment. The variable library seems like it would be a perfect solution, but the way my configuration is set up, I'd need a way to be able to dynamically choose which variable from the library to use, based on which configuration I'm using.
The ability to select a variable from the library dynamically in the pipeline instead of only statically would provide a great deal more flexibility.
frithjof_v
on:
Capture calling context (workspace, item id, item ...
on:
Allow the disabling of Job Schedule support in Git
miguel
on:
Jestor .mez connector not recognized in Power BI S...
YSD
on:
[Microsoft Fabric] Support incremental copy for Ku...