terraform-backend-git
terraformer
terraform-backend-git | terraformer | |
---|---|---|
2 | 109 | |
175 | 11,797 | |
2.3% | 1.2% | |
4.2 | 7.6 | |
5 months ago | 7 days ago | |
Go | Go | |
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-backend-git
-
GitLab for state management
I haven't used this before (not in production, but I did some tests and POCs) but if you don't want to use GitLab or any specific state management, you can use something like this: https://github.com/plumber-cd/terraform-backend-git
-
When automating a deployment involving Terraform, the common pattern is to store the state on a shared storage. What is the reason for not using a git private repository instead?
You seem pretty hell bent on doing it your way instead of the myriad other options provided and supported by hashi and/or the community so go for it, at least one other person already had the same idea.
terraformer
-
Top Terraform Tools to Know in 2024
Terraformer is a CLI tool developed by Google that generates Terraform files from existing infrastructure (reverse Terraform), simplifying the process of adopting Terraform in existing environments and speeding up the initial setup process. Terraformer supports multiple cloud providers, including AWS, Google Cloud, Azure, and others.
-
Terraformer + refactoring with 'moved' blocks
Looking into efficient ways to import existing infrastructure. Using Terraformer to get the everything into Terraform and then refactoring into modules, for_each, etc. using moved blocks seems like it would be a good approach. Refactoring them to use existing modules from providers will take a little work and likely going back and forth with terraform plan, and assuming many things won't translate straight across because of what resources a module might be creating and how they are creating them.
-
The Future of Terraform: ClickOps
We had thought about the ability to convert HCL to Go, but not much thought in querying existing infra to generate HCL (like terraformer). If you want to experiment building on top of Lingon then please go ahead! I’d be happy to help provide the context from Lingon.
-
How do you glue Terraform resources together?
If "ClickOps" is your starting point, as you mention, you could try creating a new scratch cloud provider account, do all your "ClickOps", then use a TF export tool (e.g., Terraformer) to see the exported TF resources to find all the references to other TF resources in the cloud resource dependency chain.
-
Strategies for converting an existing deployment to IaC?
I haven't worked with any of the ones that purport to work with AWS, but a quick Google shows terraformer and Terracognita as options - maybe look into trying those out?
-
Migration to gcp from aws.
This maybe a bit more complicated if you're not into coding/terraform but I'd use terraformer to convert all of your infrastructure from implementation to code while in AWS, then switch providers and with a bit of jiggly of the code implement your infra into gcs as IaC and keep it that way if/when you switch again.
-
Quick terraform noob question about the tfstate
Maybe terraformer could help. I never tried it personally . https://github.com/GoogleCloudPlatform/terraformer
- Possible to backup entire Okta configuration?
-
How do I convert my CloudFormation template into a Terraform file?
I've been wondering if this tool is any good. https://github.com/GoogleCloudPlatform/terraformer/blob/master/docs/aws.md
-
Migrate from terragrunt to terraform
If you've to write the code (I assumed you just needed to reorganize it without TG) maybe consider https://github.com/GoogleCloudPlatform/terraformer
What are some alternatives?
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.
terracognita - Reads from existing public and private cloud providers (reverse Terraform) and generates your infrastructure as code on Terraform configuration
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
former2 - Generate CloudFormation / Terraform / Troposphere templates from your existing AWS resources.
infracost - Cloud cost estimates for Terraform in pull requests💰📉 Shift FinOps Left!
terraforming - Export existing AWS resources to Terraform style (tf, tfstate) / No longer actively maintained
terraform-provider-aws - The AWS Provider enables Terraform to manage AWS resources.
gardener - Kubernetes-native system managing the full lifecycle of conformant Kubernetes clusters as a service on Alicloud, AWS, Azure, GCP, OpenStack, vSphere, KubeVirt, Hetzner, EquinixMetal, MetalStack, and OnMetal with minimal TCO.
terraform-provider-aws - Terraform AWS provider [Moved to: https://github.com/hashicorp/terraform-provider-aws]
aws2tf - aws2tf - automates the importing of existing AWS resources into Terraform and outputs the Terraform HCL code.
aztfy - A tool to bring existing Azure resources under Terraform's management [Moved to: https://github.com/Azure/aztfexport]