> Mildly complex logic constraint
> Attempt to encode in variable constraints
> Compiler too dumb to realize what I'm doing
> Figure out a check resource and assertion provider
> Terragrunt swallows the error

Terraform, not even once

#Terraform #Terragrunt

The more I work as a Dev Ops / Platform Eng, the more I fight a single anti-pattern.

For your future self :
1. Use #terragrunt and not only #terraform / #opentofu ,
2. Centralize you #tf code in different modules in a single repository and have #tg use them ,
3. That one goes without saying but here it is : DRY your code using locals !

I'm tired of removing hundred lines of #IaC code just for the sake of maintainability.

#terragrunt #finops and terraform is killing me today.

But I got the digest out,

Enjoy.

I made fun of #jdvance. It was fun. I promise

https://thistleandmoss.com/p/what-survives-the-morning-the-losers-tantrum-empire-bleeding-out-plastic-in-the-formula-and-the-lawy

Any #terragrunt persons out there?

I need a modular way to build a framework for building AWS accounts (with required services), that is DRY and repeatable.

best I can come up with:

├── _example-account
│   ├── account.hcl
│   ├── us-east-1
│   ├── us-east-2
│   ├── us-west-1
│   └── us-west-2
├── _templates
│   ├── account.hcl
│   ├── env.hcl
│   ├── region.hcl
│   └── service
├── modules
└── terragrunt.hcl

#devops #terraform

When you build a #terragrunt compliant stack of modules that can be used in any case for any capacity, and your engineers still use #clickops.

Why? oh why do they do this?

Here I am working today, on stupid #devops shit, when , and I am shocked to have to say this, but a Senior Architect tells me and I literally quote "Wendy, I dont understand #DNS nearly as good as you do, so can you help me understand the cadence of what goes first or second", and all I can think is, this guy is a developer and he stupidly asks me this question? how in the fuck?

#aws #terragrunt #terraform #opentofu #git #gitproblems #gitops #wtf