terraform-provider-aws VS terraform-exec

⚠ 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

You still have to call the terraform CLI, and as others suggested, terraform-exec is good (we use it with Lingon).

Debugging has actually been ok because all Lingon does is dump the HCL/YAML. For Kubernetes we shell out to kubectl and for Terraform we wrote a simple wrapper around terraform-exec that is not part of the core library. So when things go wrong, you're back to your basics.

I'm new to Go, and since I work pretty heavily with Terraform, I thought making some terraform automation with Go would be a great little side project/lab for learning. With that said, I'm wondering if anyone has had any luck using the terraform-exec library from hashicorp (https://github.com/hashicorp/terraform-exec). I'm finding the documentation incredibly hard to follow when trying to replicate some simple CLI commands like terraform plan and extract anything meaningful from it.

We will utilize this nice wrapper hashicorp/terraform-exec to apply the synthesized Terraform module from Go.

[hashicorp/terraform-exec sounds like what you're looking for if writing Go is okay](http://"GitHub - hashicorp/terraform-exec: Terraform CLI commands via Go." https://github.com/hashicorp/terraform-exec)

I am using a vendor from GitHub if I have to be specific this repo.

Hashicorp has their own module for doing this you might find useful: https://github.com/hashicorp/terraform-exec