terraform-provider-aws VS terraform-provider-azurerm

⚠ There is currently an issue where the additional_configuration block order causes differences when applying the Terraform configuration without making any changes.

For Terraform, instead, a new version of the AWS module supports a dedicated resource.

If we check the support for the Terraform AWS Provider here (state for the date of publishing this article), we will see that the service is not yet fully supported. Last week, after more than half a year, support for creating a policy store was added. Additionally, we have the configuration to add template policies. However, the identity source is in the form of a PR draft, and there is no PR yet for the ability to create policies.

https://github.com/hashicorp/terraform-provider-aws/issues/3...

The size is what you get when you add every single AWS Go client into one binary.

Each service client like 1-2MB. But when you have 200 services....

Issue with EC2 Instance Metadata running inside Container

Well, at least we now have a promising lead. Some diligent googling and browsing through Github issues in the AWS provider project yielded no directly related findings. However, I did come across a few recent bug reports about the recent change AWS made regarding the treatment of public buckets. And interestingly, they described precisely the behavior I was encountering.

Latest version of TF but seems to be same Issue as this which has already been submitted : https://github.com/hashicorp/terraform-provider-aws/issues/10611

Look at this; I think the provider is just screwed up: https://github.com/hashicorp/terraform-provider-aws/issues/28672

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