|about 2 months ago||3 days ago|
|Apache License 2.0||Apache 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 Plugin Framework Development: How to implement nested attributes?
5 projects | reddit.com/r/Terraform | 11 Apr 2022
In the case of the Google Cloud Platform provider, folks at Google built magic modules with the explicit goal of being able to generate schemas and behaviors for a Terraform provider and for other systems with similar needs. Since the vendor was explicitly aiming to support Terraform, this was the most ideal case where the schema could be designed to contain all of the information needed to generate a functional, usable provider.
Terraform 1.0 Release
33 projects | news.ycombinator.com | 8 Jun 2021
For GCP, both ansible modules and terraform modules are actually generated from https://github.com/GoogleCloudPlatform/magic-modules, so their "production readiness" are the same.
I understand that mitchellh himself personally created a bunch of cloud modules for terraform at the beginning, and those were likely of higher quality than whatever created by some internal developers assigned by Google/Microsoft, and might be slightly better than the AWS modules maintained by community.
Anyway, when it comes to ansible versus terraform, we shall move the discourse to states management instead. With ansible, you don't have to deal with states, but will need to clean up the cloud resources separately. With terraform, you can use the tool to clean up the cloud resources easily, but then you also have the headache of managing states. Plus, whenever you change something, there is always the nagging feeling that it will do a destroy/recreate instead of an in-place update.
5 projects | news.ycombinator.com | 20 Apr 2021
The Terraform provider for Google Cloud uses partial autogeneration, here is the repo that does the autogeneration for multiple automation tools:
What are some alternatives?
attr_json - Serialized json-hash-backed ActiveRecord attributes, super smooth
desktop-ansible - Ansible Playbooks to install Arch on my PC from scratch
terraform-ls - Terraform Language Server
terraform-cdk - Define infrastructure resources using programming constructs and provision them using HashiCorp Terraform
pulumi-provider-boilerplate - Boilerplate showing how to create a native Pulumi provider
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
kubernetes-cluster-setup-using-terraform-and-k3s-on-digitalocean - Demonstration of how you can use set up your Kubernetes cluster on DigitalOcean using Terraform + k3s + Ansible
Pulumi - Pulumi - Universal Infrastructure as Code. Your Cloud, Your Language, Your Way 🚀
aws-cloudformation-resource-providers-rds - The CloudFormation Resource Provider Package For Amazon Relational Database Service
terraform-lsp - Language Server Protocol for Terraform