Bartłomiej Danek
Author ProfileClaim This Author Profile
Prove ownership by publishing #HashtagPLUS and this profile link on your author page or an article under your byline. A moderator or admin will review the request before it merges into your real HashtagPLUS username.
🌐 dev.toSource
From Dev.to - aws: Smart DNS: Auto-Detecting Route53 Records in Terraform
🌐 dev.toSource
Terraform dynamic blocks dynamic generates repeated nested blocks from a variable - avoids copy-pasting the same block for each item. variable "ingress_rules" { default = [ { port = 80, protocol = "tcp", cidr = "0.0.0.0/0" }, { port = 443, protocol = "tcp", cidr = "0
🌐 dev.toSource
Terraform lifecycle rules lifecycle controls how Terraform creates, updates, and destroys a resource. resource "aws_db_instance" "main" { identifier = "main-db" lifecycle { create_before_destroy = true prevent_destroy = true ignore_changes = [passw
🌐 dev.toSource
.terraform.lock.hcl - commit it Terraform generates this file on terraform init - it pins the exact provider versions and their checksums so every team member and CI run uses the same binaries. provider "registry.terraform.io/hashicorp/aws" { version = "5.50.0" constrai
🌐 dev.toSource
Terraform S3 backend with state locking S3 stores the state file, DynamoDB handles locking - prevents two apply runs from corrupting state simultaneously. terraform { backend "s3" { bucket = "my-tf-state" key = "prod/terraform.tfstate" region
🌐 dev.toSource
Terragrunt dependency and mock_outputs dependency block Reads outputs from another Terragrunt unit - cleaner than terraform_remote_state and aware of the apply order. # environments/prod/eks/terragrunt.hcl include "root" { path = find_in_parent_folders("root.hcl")
🌐 dev.toSource
Terragrunt folder structure and include Terragrunt projects split config into two layers: a root hcl file with shared settings, and per-unit terragrunt.hcl files that inherit from it. root.hcl environments/ ├── dev/ │ ├── vpc/ │ │ └── terragrunt.hcl │ ├── rds/ │ │ └