Deployment pipeline: Deployment rules for Direct Lake on OneLake semantic models

The docs now show an alternative to data source rules by updating the semantic model with M Parameters and using Parameter Rules: 

https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-develop#use-m-parameters-with-deployment-pipelines

This should be helpful for most of the cases.

Would love to see this get fixed. Really would be helpful to have an autobinding solution, but i would be happy with a deployment rule or variable library solution. When can we expect resolution? 

The lack of native deployment rules for Direct Lake on OneLake semantic models significantly impacts CI/CD processes and currently requires custom post-deployment workarounds.
Is there any update on when Microsoft plans to address this issue?

I'm amazed at how long it's been since the launch of Direct Lake connections and the identification of this bug, yet Microsoft still hasn't been able to fix it. This isn't a new feature; it's a fix for something that works for various sources but no longer works for Direct Lake connections (this one encouraged by Microsoft!). I hope to see this bug fixed soon. Most of the available workarounds aren't ideal yet.

We had to implement a deployment pipeline from azure devops, using the python cicd library (now fully supported by microsoft). To change the data sources on release we used a powershell script to do a string replace on the expressions.tmdl file and any other sources in the tables folder. This actually works and doesnt come with any limitations (unlike the parameters method). I believe this is the only way to deploy direct lake on onelake models.

I had about 5 phone calls and an email chain about 30 messages back and forth with microsoft support. It took a number of attempts them to to understand what I was even talking about. In the end the conclusion was they didnt have any solution, and anythign suggested by them was just pointing to blog posts already linked to here, so I wouldnt recommend trying to get support for this.

Feel free to ask questions on how we managed to achieve a working pipeline. When I first began it seemed like a minefield and lots of unclear information on what to do.