terraform-provider-aws VS roadmap

⚠ 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

Good to see, waiting on https://github.com/opentffoundation/roadmap/issues/8 so can do some testing (yes can build from source, but I'd rather use the releases)

Not the OP, but I suspect HN has trimmed the anchor link.

> https://github.com/opentffoundation/roadmap/issues/24#issuec...

That's the comment that made the issue clear -- specifically TOS were amended for https://registry.terraform.io to state:

> You may download providers, modules, policy libraries and/or other Services or Content from this website __solely for use with, or in support of, HashiCorp Terraform.__

ie., it looks like the intent is "You can't use OpenTF with registry.terraform.io".

IMO, that feels a little petty. But, I guess if OpenTF is taking a position of "Use us instead of Terraform", then they shouldn't expect to get the usage of Hashicorps infra.

Making sure there aren't any trademark infringements left, that we have some basic community process in place, etc.

There's unfortunately a bunch of these things we have to do before we can publish. We created a public roadmap repo if you'd like to track the progress[0]. We're doing our best to make it public as soon as possible.

[0]: https://github.com/opentffoundation/roadmap/milestones

Disclaimer: Work at Spacelift, and currently temporary Technical Lead of the OpenTF Project, until it's committee-steered.