Issues with changing the workspace ID when versioning.

[michelmetran]

I'm working on versioning the changes in my workspace in a Git repository.

My production workspace (PROD) is linked to the main branch.

I have other development workspaces (DEV) that represent other branches.

In the production workspace, in addition to the lakehouses, I also have a database, and I want to consume information from this database in the other branches as well. To do this, I created a shortcut to the database schema (from the main branch workspace) in the lakehouse of the DEV workspace.

However, whenever I make a Pull Request transferring changes from the DEV branch to the PROD branch, Fabric modifies the shortcuts.metadata.json file... keeping the Workspace ID as "workspaceId": "00000000-0000-0000-0000-000000000000", and changing parameters....

Because of this, I can never get the DEV and PROD branches synchronized, since Fabric changes the parameters...

There's always a pending change in the main branch (PROD) that was supposedly made in the main branch itself, which is not a good practice for versioning code...

[KevinChant]

If you look to use fabric-cicd instead of the branch merging strategy you can filter out which items are moved over. Hope this helps