terraform-provider-azurerm VS bicep

So this is doing my head in. Related to https://github.com/hashicorp/terraform-provider-azurerm/issues/6117

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

There are different Terraform Providers that enable Terraform to interact with Microsoft Azure. The most common one are Azure Stack, AzureDevops, AzureRM, AzAPI and AzureAD.. In this tutorial, we use the AzureRM Terraform Provider. Let's create a Terraform file for the AzureRM Terraform Provider.

Yeah we imported all the related resources. I could now find an issue, which exactly describes our problem. Unfortunately it is open since 2020: https://github.com/hashicorp/terraform-provider-azurerm/issues/8794

Like other people said, use the azurerm provider docs, they're pretty good. But that's where knowing Azure comes in handy because you'll have to figure out what TF resource to use to accomplish a given goal.

It’s not difficult at all syntactically. But you must understand the provider you are automating. So your azure knowledge is key in this case. Read the Azure provider docs and you will be easily able to put something together. https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs

I thought it was a good idea, but Bicep did not agree. I have submitted a proposal to the Bicep team for how this can be allowed. Vote for this issue if you agree!

Bicep has limitations which makes it non-declarative even though it is marketed as declarative: https://learn.microsoft.com/en-us/azure/azure-resource-manag...

MSFT is trying to add features to make this better, but it is not in production yet: https://github.com/Azure/bicep/issues/10460

Additionally, Bicep does not support interacting with Azure Active Directory: https://github.com/Azure/bicep/issues/7724

So it really is not very useful. Terraform is better in almost every single conceivable way.

Github: https://github.com/Azure/bicep/issues/9569

Since its launch Bicep has become popular within the IT community. You can find blog posts, tweets, conference sessions, and plenty of interaction on the official Bicep GitHub space. Bicep became production ready at v0.3. It is supported by Microsoft Support Plans.

Please give Azure Bicep a try. You get a really simple experience with all the benefits of using the platform native capabilities https://github.com/Azure/bicep

I was on the bicep call last month but that doesn't mean I didn't miss the announcement, it looks like they are getting close though - https://github.com/Azure/bicep/issues/8598

Bicep, the open source project used by Visual Studio Code to extend its capabilities, has finally arrived in Visual Studio, enabling users of Microsoft’s flagship IDE to use some of Bicep’s most popular features in the same program they have been using since they were introduced to it — in other words, Visual Studio itself.

In addition, check the similar issue on GitHub.

There is an ongoing thread here https://github.com/Azure/bicep/issues/1853