Chapter 8. Evolving Projects Into Enterprise
Each organization has a unique experience adopting IaC, but they often have the same few characteristics: they either start with a single TF project and end up with a massive module and state, or they start with multiple projects but end up collecting most of their components into the most active one, and still end up with a massive module and state. At some point, the team becomes overwhelmed with endless merge conflicts, locked states, or an elaborate review procedure that requires multiple Git branches or tags to track effectively. In many cases, this causes a panic when things go wrong around a major release or when there is a significant exposure of sensitive information. The choice then becomes fairly binary: hire consultants to evaluate the existing system, create a plan of action, and execute, ideally, within the constraints laid out in the contract and likely over multiple quarters; or take on the initiative, internally—after all, you already have the domain knowledge and know where all the problem areas are and what all the possible procedural snags will be.
The purpose of this chapter is to expose you to the various factors and indicators that influence the need to split. Whether or not you start with a single project, it’s important that you recognize the likelihood that you will need to split or reorganize your infrastructure into multiple root modules and organized into layers or a hierarchy. You should start tracking, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access