Fabric API for committing warehouse items is a pain.

[joengelhartdev]

I have a pipeline that makes api calls to force fabric after a git checkin to update the fabric workspace but continue to run into issues when it's warehosue related. Please fix this. See below:

• The issue is that “deploy the Warehouse” and “clear Fabric Source Control sync state” are not the same operation.

Your latest run proves this:

- The pipeline did deploy the Warehouse.
- sqlpackage published successfully.
- The failure happened after that, when the pipeline rechecked Fabric git/status.

So the broken part is not the Warehouse publish anymore. The broken part is Fabric Source Control reconciliation.

What is happening:

1. The pipeline publishes the Warehouse schema directly to Gold_Management.
2. That changes the actual Warehouse.
3. But Fabric workspace Git metadata still says the workspace head is old:
- workspaceHead = 827488413510f0a52a4458270c4
- remoteCommitHash = 989196d7abfcbbf86e1d3fea
4. The pipeline then asks, “can I finish the Git sync?”
5. The answer is still no, because app-only updateFromGit on a pending Warehouse item is the exact Fabric path that returns PrincipalTypeNotSupported.

So the issue is:

- app registration can deploy the Warehouse
- app registration cannot clear the Fabric workspace Git sync state for Warehouse items through updateFromGit

That is why the run says:

- publish succeeded
- sync still pending
- stop

So if your expectation is “the pipeline should both deploy and mark Fabric Source Control fully synced,” that is the part Fabric is blocking under app-only
auth.

The current failure is not a code bug anymore. It is a platform limitation around Fabric workspace Git sync for Warehouse items under app-only auth.

Sources:

- Fabric updateFromGit: https://learn.microsoft.com/en-us/rest/api/fabric/core/git/update-from-git
- Fabric Warehouse service principal support: https://learn.microsoft.com/en-us/fabric/data-warehouse/service-principals
- Fabric Warehouse deployment with SqlPackage: https://learn.microsoft.com/en-us/fabric/data-warehouse/development-deployment

If you want, I can make the policy change now so pipeline 1363 succeeds after a successful Warehouse publish and only emits a warning about stale Fabric Source
Control state.