terraform-provider-vra
terraform-provider-aws
Our great sponsors
- Onboard AI - Learn any GitHub repo in 59 seconds
- InfluxDB - Collect and Analyze Billions of Data Points in Real Time
- SaaSHub - Software Alternatives and Reviews
| terraform-provider-vra | terraform-provider-aws | |
|---|---|---|
| 2 | 96 | |
| 89 | 8,997 | |
| - | 1.4% | |
| 0.0 | 10.0 | |
| 29 days ago | 6 days ago | |
| Go | Go | |
| Mozilla Public License 2.0 | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terraform-provider-vra
We haven't tracked posts mentioning terraform-provider-vra yet.
Tracking mentions began in Dec 2020.
terraform-provider-aws
-
HashiCorp silently amend Terraform Registry TOS
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....
-
A Cloud Development Troubleshooting Treasure Hunt
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.
-
Converting Full Terraform Programs to Pulumi
> We're coming up on 10000 resources in our main Terraform repository and while there is definitely some friction, it's overall much better than having to hit the cloud API's to gather each of those states which would probably take at least an order of magnitude longer.
I don't think that's necessary true. Most cloud API's actually can return hundreds of records with 1 API calls, e.g. https://docs.aws.amazon.com/elasticloadbalancing/latest/APIR... has a maximum page size of 400.
If I manage the cloud resources via some custom tools and/or with some ansible-fu, I can decide to batch the API calls when it makes sense.
With terraform, it is not possible to do so (https://github.com/hashicorp/terraform-plugin-sdk/issues/66, https://github.com/hashicorp/terraform-provider-aws/issues/2...).
-
HEADS UP: Terraform AWS Provider 5.0.0
Release notes - https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0
The only footgun I know of is changing the behavior of RDS instances created from snapshots. Force replacement on snapshot_identifier change for DB cluster resources will fuck up your world if you use a data source for snapshot_identifier since yesterday it would ignore any updates and today it will happily destroy your database (and, because AWS, all of the automated snapshots thereof) when the data identifier changes out from under it. 🎉
-
Any tools out there, or better ways, to unit test IAM policy documents?
A while back I wrote a PR for the AWS provider to expose the policy simulator directly inside Terraform: https://github.com/hashicorp/terraform-provider-aws/pull/25569
-
Weird warning after running pulumi preview
The reason you see that is because the AWS Classic provider (pulumi_aws) is built on top of the open-source terraform-provider-aws (via the Terraform bridge you identified), and terraform-provider-aws is emitting that notice at runtime. Not all Pulumi providers are built from Terraform providers, however, but some, like this one, still are. (There's a notice at the bottom of the page for each resource where this is the case.) It works like this:
-
Script or software that automatically populate specific profile in ~/.aws/credentials
See: * https://github.com/hashicorp/terraform-provider-aws/issues/10491 * https://github.com/Sceptre/sceptre/issues/674
-
Issue with aws_s3_bucket_replication_configuration
I'm having an issue with aws_s3_bucket_replication_configuration similar to https://github.com/hashicorp/terraform-provider-aws/issues/23487 but not 100% sure what the I'm doing wrong as its listed as fixed there.
This suggests to me that what you did should be valid, because you didn't write a replication_configuration block inside the aws_s3_bucket resource block. Therefore I think this is a bug in the provider, which you may wish to report in the provider's GitHub repository.
What are some alternatives?
crossplane - Cloud Native Control Planes
terraform-provider-lastpass - Terraform Lastpass provider
cognito-custom-email-sender-lambda - AWS Cognito custom email sender Lambda trigger
rover - Interactive Terraform visualization. State and configuration explorer.
terraform-provider-opsgenie - Terraform OpsGenie provider
terraform-provider-snowflake - Terraform provider for managing Snowflake accounts
semgrep - Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.
zeal - Offline documentation browser inspired by Dash
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
terraform-exec - Terraform CLI commands via Go.
dash-contrib-docset-feeds - A collection of Dash's user contributed docset feed for using with Zeal
helmfile - Deploy Kubernetes Helm Charts