Best practices for modularizing a Terraform project | PlatformCon 2023

In this talk, I will share Terraform best practices to optimize Infrastructure as code. Using real-world examples from my experience using Terraform, I will explore common challenges and anti-patterns by providing practical strategies to overcome them.
Terraform is a popular tool for managing Infrastructure as code. Therefore, it's essential to consider modularizing your Terraform code to make it more organized, maintainable, and scalable. I will explore some best practices for modularizing a Terraform project in this talk.
We'll start by discussing the importance of defining a clear project structure that reflects the logical components of your infrastructure and explore Terraform anti-patterns by providing best practices for avoiding them.
We'll then dive into using modules to encapsulate resources. I will also cover the use of variables to parameterize your code and make it more flexible, as well as the use of outputs to expose values to other modules.
Speaker: Vjosa Fusha
System Reliability Engineer, Moss
_____________
- Check all the PlatformCon talks: platformcon.co...
- Check all the PlatformCon tracks: platformcon.co...
- Join Platform Engineering Slack: platformengine...
#PlatformCon2023 #PlatformEngineering

[@kenwizspoila6870]

Very Insightful. That was an articulate presentation on why you implemented the practices you highlighted.

[@rootgrrrl9698]

Useful content, thanks!

[@igor9silva]

Content was truly great, but Vjosa needs some energy 🥵

[@sabry5106]

Thanks

[@jackweaver5840]

so where does the provider configuration go into? do I need to define it in each main.tf? (which can result in code duplication) or have it in main.tf in the root?

[@mariomp4973]

Hello, how are you, a question, we have a backend state per environment (dev, qa, prod) but the demand for infra from the teams is growing, so we have 5 areas that each area has its development and infra team, and my question is Would it be better to create backend state for each area? Is it a good practice? to not have a single backend state per environment? thank you