←back to thread

Duplication Isn't Always an Anti-Pattern

(medium.com)
52 points birdculture | 1 comments | 02 Dec 25 08:58 UTC | HN request time: 0.196s | source
Show context
jamesbelchamber ◴[07 Dec 25 14:50 UTC] No.46182053[source]▶
"Don't Repeat Yourself" is a great rule of thumb which, at least in writing Terraform configuration, became absolute tyranny. Strange webs of highly coupled code with layers of modules, all in an effort to be DRY - almost everywhere I've seen Terraform.

Trying to explain why a little duplication is preferable to bad abstractions, and specifically preferable to tightly coupling two unrelated systems together because they happened to sort-of interact with the same resource, was endless and tiring and - ultimately - often futile.

replies(6): >>46182179 #>>46182504 #>>46182524 #>>46182757 #>>46182935 #>>46183063 #
1. Ekaros ◴[07 Dec 25 16:50 UTC] No.46183063[source]▶
I don't do too much terraform. But isn't the DRY really happening on provider level? And when you are using it, most of times it really doesn't make too much sense to try to not repeat yourself. Unless you are dealing with actual identical resources. Or deploying multiple times say dev, test and prod.