Folder structure and ADO/Fabric sync

We have a similar workspace structure (except we have separated code into its own workspace)

We have folders in the DevOps repo that match the layers and the process/code workspace.  Lakehouses don't generate much in the way of artifacts - just a stub entry really.

The main branch is connected to the dev workspaces.

We've declined (for now) to use the Deployment Pipelines and are instead going to use two branches - test and release - to connect to our test and prod environments.

The biggest issue you'll find in general is trying to rewrite the default lakehouses of any artifacts.  Yes deployment rules do work, but you have to currently maintain them separately.  This is likely to change in the future with some of the stuff on the roadmap.  We are currently looking at a couple of ways around this involving absolute lakehouse paths and API calls to change the default lakehouses.

In terms of synching branches to main, it's possible to set up DevOps scripts that are automatically triggered on pull requests to perform a synch (and/or trigger semantic model refreshes) once the pull request has executed.

There are some things in the roadmap that will make things easier for deployment pipelines (such as parameters)