hwaog.blogg.se - Allplan quickstart

(read_terragrunt_config) Reusing dependencies.(read_terragrunt_config) Keeping remote state configuration DRY.

dynamodb_table_config block that populates dynamodb.CreateTableInput struct.dynamodb_table_config block in remote_nfig.Option 3: scaffolding tool that code gens live config using a template.Option 2: for_each attribute in terragrunt config that “generates” multiple copies of the config.for_each to call terraform module multiple times.A note about using modules from the registry.get_terraform_commands_that_need_parallelism.

get_terraform_commands_that_need_locking.terragrunt-fetch-dependency-output-from-state.terragrunt-include-external-dependencies.terragrunt-ignore-external-dependencies.terragrunt-iam-assume-role-session-name.The problem with mixing remote Terraform configurations in Terragrunt and lock files.The long version: details of how Terragrunt handles lock files.The short version: how to use lock files with Terragrunt.

Use-case: I use locals or dependencies in terragrunt.hcl, and the terraform output isn’t what I expected.

Configuring Terragrunt to assume an IAM role.

Limiting the module execution parallelism.

Execute Terraform commands on multiple modules at once.

Using read_terragrunt_config to DRY parent configurations.

Using exposed includes to override common configurations.

Using include to DRY common Terragrunt config.

Create remote state and locking resources automatically.

Filling in remote state settings with Terragrunt.

Keep your remote state configuration DRY.

DRY common Terraform code with Terragrunt generate blocks.

Using Terragrunt with private Git repos.

Important gotcha: working with relative file paths.

Achieve DRY Terraform code and immutable infrastructure.

Promote immutable, versioned Terraform modules across environments.