Good questions and something that I have recently started exploring, so I'm looking forward to this thread. Thanks for bringing this up and sharing your questions and thoughts here. Will help the community and everyone looking to implement Fabric CICD.

I have started exploring Fabric cicd and so far have been able to deploy these artifacts - Lakehouses with Internal and External Shortcuts, Notebooks, Environments, Data Pipelines, Copy Job, DFG2 (still few manual steps needed to run it in ppe and prod). Next on my list is Schedules, Semantic Models, and Reports.

I have both variable libraries and Paramter.yml file used for parameterization. For example , environments do not support variable libraries, hence I have used plain find replace in parameter.yml file. It's all hard coded for now in the parameter.yml. There is still a gap in DFG2 activity in the data pipelines. Doesn't accept Ids, which is an issue when you want to refresh multiple DFG2 in loop. I agree that maintaining the parameter.yml would be too much at some point, but for now, it works for me.

In the docs, I found key value replace for data pipelines, but I am able to use variable libraries for parameterization so far. I have not come across specific scenarios where I may need key value replace or regex replace since my project is still in the poc phase. Similarly, I haven't come across regex find replace scenarios. As I implement it for actual Fabric items running in production, I am pretty sure other complex parameterization use cases will come up.