- terraform-best-practices VS terraform-workspaces-aws-multi-account
- terraform-best-practices VS terraform-ecs
- terraform-best-practices VS terraform-aws-lamp
- terraform-best-practices VS terraformer
- terraform-best-practices VS terraform-azurerm-compute
- terraform-best-practices VS terraform-nixos
- terraform-best-practices VS modules.tf-demo
- terraform-best-practices VS configure-aws-credentials
- terraform-best-practices VS terraform-aws-secure-baseline
Terraform-best-practices Alternatives
Similar projects and alternatives to terraform-best-practices
-
terraformer
Discontinued CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
-
Kargo
Stop Scripting Promotions. Start Shipping with Kargo. Kargo automates promotion across dev, staging, and prod with approval gates and verification. Open source, built by the team behind Argo CD. Download now.
-
configure-aws-credentials
Configure AWS credential environment variables for use in other GitHub Actions.
-
terraform-workspaces-aws-multi-account
Building and managing AWs multi account architecture with Terraform workspaces.
-
-
-
-
terraform-nixos
A set of Terraform modules that are designed to deploy NixOS [maintainer=@adrian-gierakowski]
-
AppSignal
Monitoring that respects your time & budget. APM, error tracking, and dashboards for modern web apps. Ten-minute setup, transparent flat pricing, and support from engineers who actually use the product.
-
-
terraform-aws-secure-baseline
Terraform module to set up your AWS account with the secure baseline configuration based on CIS Amazon Web Services Foundations and AWS Foundational Security Best Practices.
terraform-best-practices discussion
terraform-best-practices reviews and mentions
-
Using Terraform Workspace for AWS multi account archtetctures
I generally consider the AWS CLI configuration to be something that's unique to a developer's workstation, and shouldn't be referenced in terraform code (in the form of tying the workspace name to your AWS profile name).
This would only work if all developers on a team have synchronised the same AWS CLI config (which to me is like asking people to synchronise dotfiles, not something I'd be willing to do).
My go-to architecture for multi-environment tends to be this, as it lends itself relatively well to Git Flow (or GitHub Flow): https://github.com/antonbabenko/terraform-best-practices/tre...
Stats
antonbabenko/terraform-best-practices is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of terraform-best-practices is HCL.