Happy New Year to all. Microsoft has deliver some new improvement for Power Platform source control that now automate some of the things we have been practicing when we implement CI/CD.
There is now an ability to connect solutions to Git (only works on Azure DevOps on the same tenant).
It could be MVP or by design, they only offer a Create without ability to Edit the connection or even remove it if you change your mind. It will ruin your environment as it will locked you down into the DevOps project and Git repo that you setup, so be very careful when doing this on an actual DEV environment. There is no UNDO, they warn you too. Hopefully they allow people to UNDO in future releases. You cannot even change the branch once you connected a solution to Git.
What it Does?
Basically, it detects changes to any configuration made in the solution; where you can then commit from the solution into the Git branch setup.
It will unpack (THE UNPACKING IS IN YML too, not the old school XML) into the branch. Best to link it to your develop branch (I was lazy and tested it on MAIN, and I am stuck with it now).
The code sync works both way too, you can make direct changes to the YML and pull it into the solution. Changing in Git Repo and Configure might cause conflict (have not tested how this works), so that is going to be a way of working to be define.
We can now revisit how we implement our CI/CD process; Bake in this new functionality which unpacks the solution into the branch.
Cons
It does not allow feature branching strategy. People might still stick with the current process of manually exporting and unpacking it.
Another issue is, you have no way to pick and choose which configuration you want to commit, it will commit all changes it detects, so changes by other developers will also go under your name when you are committing.
Top comments (0)