terraform-google-project-factory
atmos
terraform-google-project-factory | atmos | |
---|---|---|
5 | 8 | |
813 | 581 | |
0.1% | 6.4% | |
8.0 | 8.6 | |
4 days ago | 2 days ago | |
HCL | 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-google-project-factory
- Terraform docs say longstanding deployments should not use workspaces. what are your thoughts?
-
HOWTO; Connect to a private GKE cluster using a site-to-site VPN between a GCP VPC...
We use Terraform to provision all GCP resources. Google provides opinionated Terraform modules to manage GCP resources here. Our infra leverages a shared VPC and we use the project factory module to create the host project and the service projects. The VPN will be provisioned in the host project that owns the VPC. Our GKE clusters are created with the private cluster terraform module.
- Does anyone have a terraform script to enable GCP Dataproc metastore service?
-
Landing zone in GCP?
They have another that is a little less in scope for projects https://github.com/terraform-google-modules/terraform-google-project-factory
-
Terraform help / guidance for a noob.
Consider looking into Google's Project Factory module. It has options to deprivildge the default compute service account.
atmos
-
AWS Landing zone creation: manual or AWS Control Tower?
This is why we created atmos to make it easier to manage large multi-account architectures. As a result, our components are reusable across organizations, regardless of how many accounts and regions they operate, and we minimize the snowflakes. And we avoid code generation, which is hard to thoroughly test in an automated fashion. Without naming names, lots of tools for terraform rely on code generation, but I see it as an anti-pattern that should be avoided.
- How to manage terraform code for large projects?
-
Terraform | Take your Terraform skills to the next level!
sorry did not find anything advanced. A better tool to make terraform scaleable is https://atmos.tools
-
Terraform docs say longstanding deployments should not use workspaces. what are your thoughts?
Workspaces are incredibly practical, and we leveraging them at-scale with literally thousands of workspaces using atmos for terraform. There is so much FUD around workspaces that is either ill-informed or based on outdated information. Any company using terraform at scale will rely on tooling and conventions. It's up to that tooling to ensure you are using terraform safely. Atmos is one of those tools. I'm not saying that you have to use workspaces, but just that there's nothing wrong with workspaces themselves.
-
List of most useful Terraform open-source tools
Check out atmos for a fresh take at managing terraform configurations and terraform workflows. Instead of managing HCL `.tfvar` files manually for configuration, it uses YAML, and supports concepts of imports (via deep merging), remote imports (anything supported by gogetter), mixins, inheritance, multiple-inheritance, vendoring of root modules, workflows, task runners (via custom subcommands), and much more. There's a bit of a learning curve and mind-shift required if coming from a Terragrunt background, but the experience is mindblowing after switching to it. Also, it's not limited to terraform.
-
Why does Hashicorp advise against using workspaces to manage environments?
We obviously don't have a project for your exact use case, but we have an open-source example repo that shows a fairly advanced scenario of using the Terraform Spacelift Provider https://github.com/spacelift-io/demo-preview-environments-manager, a simple quickstart of using it https://github.com/spacelift-io/terraform-starter and you can also see the CloudPosse Atmos project, for a very advanced scenario which generates lot's of Stacks based on your component specifications https://github.com/cloudposse/atmos.
- Atmos
- Atmos: Universal Tool for DevOps and Cloud Automation (Terraform, Helm, etc.)
What are some alternatives?
terraform-example-foundation - Shows how the CFT modules can be composed to build a secure cloud foundation
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
terraform-google-bootstrap - Bootstraps Terraform usage and related CI/CD in a new Google Cloud organization
terramate - Terramate CLI is an open-source Infrastructure as Code (IaC) orchestration tool for Terraform, OpenTofu, Terragrunt, Kubernetes, Pulumi, Cloud Formation, CDK, Azure Resource Manager (ARM), and others.
terraform-google-kubernetes-engine - Configures opinionated GKE clusters
terraform-starter - Starter repository to play with Spacelift
terraform-google-vpn - Sets up a Cloud VPN gateway
demo-preview-environments-manager
terraform-google-lb-internal - Creates an internal load balancer for Compute Engine by using forwarding rules
akk-stack - Containerized EverQuest Emulator Server Environment
terraform-google-iam - Manages multiple IAM roles for resources on Google Cloud
ops-examples - A repository of basic and advanced examples using Ops