Type | Description | Supported by Atlantis |
---|---|---|
small | Few resources, no external dependencies. Single AWS account. Single region. Single environment. | yes |
medium-terraform | Several AWS accounts and environments, off-the-shelf infrastructure modules, composition pattern using Terraform. | yes |
large-terraform | Many AWS accounts, many regions, urgent need to reduce copy-paste, custom infrastructure modules, heavy usage of compositions. Using Terraform | yes |
very-large-terraform | Several providers (AWS, GCP, Azure). Multi-cloud deployments. Using Terraform | yes |
Type | Description | Supported by Atlantis |
---|---|---|
medium-terragrunt | Several AWS accounts and environments, off-the-shelf infrastructure modules, composition pattern using Terragrunt | yes |
large-terragrunt | Many AWS accounts, many regions, urgent need to reduce copy-paste, custom infrastructure modules, heavy usage of compositions. Using Terragrunt | yes |
very-large-terragrunt | Several providers (AWS, GCP, Azure). Multi-cloud deployments. Using Terragrunt | yes |
- Perfect to get started and refactor as you go
- Perfect for all resource modules; good for small and linear infrastructure modules (eg, [terraform-aws-atlantis])
- Great for small number of resources (fewer than 20-30)
- Single state file for all resources can make process of working with Terraform slow
- @todo: When using this with large amount of resources, resource targeting will help (
terraform plan -target=...
).
- Something good
- Something bad
- Something good
- Something bad
- Something good
- Something bad
- Something good
- Something bad
- Something good
- Something bad