Support for [Microsoft Fabric]

[mehul3446]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Description

I would like to request a resource block that creates and manages Microsoft fabric Capacities(Microsoft.Fabric/Capacities) on Azure (not to be confused with service fabric or recovery fabric). Here's a link to the documentation: https://learn.microsoft.com/en-us/fabric/

New or Affected Resource(s)/Data Source(s)

azurerm

Potential Terraform Configuration

N/A

References

No response

[pierrejeandev]

We also need to manage Fabric Capacities in Terraform.
For now we are using the Azure management API directly, but our infra-IT guys are not impressed by that and for production, they will only accept azurerm provider resources.

[smitp11]

We also need to manage Fabric Capacities in Terraform. For now we are using the Azure management API directly, but our infra-IT guys are not impressed by that and for production, they will only accept azurerm provider resources.

@pierrejeandev
Is there an example of this azapi code that you are willing to share? thanks!

[mehul3446]

We also need to manage Fabric Capacities in Terraform. For now we are using the Azure management API directly, but our infra-IT guys are not impressed by that and for production, they will only accept azurerm provider resources.

@pierrejeandev Is there an example of this azapi code that you are willing to share? thanks!

https://github.com/Azure/azure-data-labs-modules/blob/d2540c7e6b38836e0461c2956f5ca002bdcd0bbf/terraform/fabric/fabric-capacity/main.tf

[neilmca-inc]

We also need to manage Fabric Capacities in Terraform. For now we are using the Azure management API directly, but our infra-IT guys are not impressed by that and for production, they will only accept azurerm provider resources.

Just wondered what their concern is? Not as an excuse, but a Azure API direct is about as close to the metal as you can get - before anyone writes an AzureRm provider version on the top of it

I sometimes think should I just use the azapi_resource for everything - as it's exactly what an ARM or Bicep template would do - but with the added bonuses of being supported day-one AND change/state management using Terraform

[tombuildsstuff]

Looks like the API isn't documented for this one - I can't see Microsoft.Fabric within the Azure/azure-rest-api-specs repository.

Azure/azure-rest-api-specs#27245 suggests that this RP may have been renamed from Microsoft.PowerBIDedicated - but that the payload isn't compatible, as such we'd need the Service Team to document their API so that an SDK can be generated/we can use that in the Provider here, hence the labels.

[DariuszPorowski]

@tombuildsstuff Microsoft Fabric ARM APIs are on the roadmap (https://learn.microsoft.com/en-us/fabric/release-plan/shared-experiences#microsoft-fabric-arm-apis). Estimated release timeline: Q3 2024

[tombuildsstuff]

Looks like these got merged as of: Azure/azure-rest-api-specs#29355

[jhutchings]

Looks like these got merged as of: Azure/azure-rest-api-specs#29355

Looks like it's showing up as a PR in Pandora in a PR now hashicorp/pandora#4372

[jhutchings]

@tombuildsstuff are the upstream labels for blockers still accurate? I believe the blockers from Microsoft are now resolved but integration of the Pandora PR is the next so either upstream/pandora / upstream/go-azure-sdk or sdk/not-yet-supported?

Sorry hoping to get this implemented as we have internal interest in the resource and I'd prefer not to do a workaround and leverage azapi or something else and have to backport those projects to a TF implementation at a later time.

I do understand that the v4 release has likely slowed some of these features as Hashi may not want to introduce too much new at a time of existing flux and probably a lot on the table in terms of migration support and such.

[jhutchings]

Yay Pandora has merged the branch 9 hours ago! 🎉
Looks like SDK PR is next step 👍
hashicorp/go-azure-sdk#1074

[T0biii]

The SDK PR with Fabric got merged also: hashicorp/go-azure-sdk#1075
🎉

[jarpoole]

There is also now an experimental provider available! See https://registry.terraform.io/providers/microsoft/fabric/latest/docs

[dtheodor]

The fabric terraform provider has nothing to do with the fabric capacity, it concerns internal fabric artifacts. Fabric capacity is azurerm territory.

Can you expedite this?

[DariuszPorowski]

Support for Fabric Capacity has been addressed in the PR #28080 (kudos goes to @sinbai) and shipped in the recent release v4.14.0 🚀

docs: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/fabric_capacity