Feature Workspace -> Main Git Deploy fails on shortcuts and leave hanging resources

[johncfabric]

I am working with feature workspaces that are based on the main. 

Inside feature workspace #1, we have a set of lakehouses that we are adding as part of the feature. The lakehouse shortcuts data from a lakehouse in another feature workspace #2. When moving the PR'ing the feature from #1 to main, we changed the target of the shortcut to take data form the main workspace rather than the feature branch. 

Not all tables existed in main that existed in branch, and thus the resource deployment of in main of the new lakehouse failed on shortcut creation. This caused the lakehousename.Lakehouse to fail. the error in this message is as follows: 

Shortcut operation failed with due to following errors: Shortcut operation failed due to error code RequestBodyValidationFailed and error message Target path doesn't exist.

After fixing the shortcut, on redeploy I get an error that Workload Error Code DatamartCreationFailedDueToBadRequest

Workload Error Message Datamart creation failed with the error 'The name is already in use'.

This error is due that the SQL endpoint and semantic model for the Lakehouse was created before the Lakehouse itself was created. I now cannot deploy anything to main branch, as source control states that updates to code are needed.  

It has bee 24 hours, the resources are not there, it is not possible to delete the SQL Endpoint and semantic model manually. The Fabric CLI excludes SQL Endpoints and Semantic models from the delete functionality(fab rm lakehouse.SQLEndpoint ->  rm: [UnsupportedCommand] not supported for command 'del') 

I also tried moving the resources and renaming them, but this was also not possible to execute. 

How should these be cleaned up so the Main branch is clean and matches the working directory?

[v-prasare]

@johncfabric ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?

Thanks,

Prashanth Are

MS Fabric community support

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query

[v-prasare]

@johncfabric ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?

Thanks,

Prashanth Are

MS Fabric community support

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query

[v-prasare]

@johncfabric ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?

Thanks,

Prashanth Are

MS Fabric community support

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query

[v-prasare · Accepted solution]

Hi @johncfabric,

Fabric CLI does not allow you to delete SQL Endpoints or Semantic Models.

To remove these, Can you try using Microsoft Fabric REST API once and let me know if this helps?

• First, call the GET API to list all items in your workspace.

• The URL for this is:
  https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/items

• From this list, find the item ID of the SQL Endpoint or Semantic Model that you want to delete.
• Then, use the DELETE API to remove the specific item.

• The URL for this is:
  https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/items/{itemId}

To use these APIs, make sure you are signed in with an account that has the right permissions, like a Service Principal or a user with Fabric Contributor rights. You will also need a valid Azure AD access token for authentication.

Thanks,

Prashanth Are

MS Fabric community support

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query

[johncfabric]

Thanks for this update Prashanth. The auto cleanup function of azure eventually removed this resource, it just took 36 hours for the process to execute. 

I will mark this as the accepted solution and follow it if I have a problem like this in the future.