Terraform Patterns, Observed

While Terraform is primarily a configuration language that abstracts the APIs of another platform, there are logic expressions available in Terraform allowing developers to introduce inferences and abstractions, improving the flexibility (or general accessibility) of a solution, without introducing repetitive code or requiring deep technical knowledge on behalf of a module’s consumer. However, the tendency to see each of the world’s problems as a nail once one’s hammer is mastered can lead a team into a quagmire of complexity. On the other side, a draconian forbiddance of Terraform expressions can force teams into developing unreasonably large and repetitive codebase or splitting a team’s overall state into a vast wilderness of Terraform state trees. In this post, we will discuss the most likely places for logic to appear, the major contributors to code complexity and developer confusion, and some gentle suggestions on how one might address or approach the spread of logic. <a href="https://medium.com/devoops-discourse/terraform-patterns-observed-part-5-logic-in-terraform-a0b1207b3a56">Visit Now</a>