{"id":2846,"date":"2026-05-20T09:30:00","date_gmt":"2026-05-20T09:30:00","guid":{"rendered":"https:\/\/mugnos-it.com\/?p=2846"},"modified":"2026-05-06T12:59:36","modified_gmt":"2026-05-06T12:59:36","slug":"from-modules-to-intelligence-the-next-step-in-terraform","status":"publish","type":"post","link":"https:\/\/mugnos-it.com\/pt\/from-modules-to-intelligence-the-next-step-in-terraform\/","title":{"rendered":"From Modules to Intelligence: The Next Step in Terraform"},"content":{"rendered":"
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n

There’s something I never thought I would say\u2014but today, I proposed an architecture that challenged one of my own long-standing beliefs.<\/p>\n\n\n\n

For years, working with large enterprises and global companies, I was one of the main advocates for Terraform standardization through reusable modules<\/strong>. The reasoning was clear: consistency, reusability, governance, and reduced cognitive load.<\/p>\n\n\n\n

And to be fair\u2014all of that is still true.<\/p>\n\n\n\n

But today, I caught myself questioning something fundamental:<\/p>\n\n\n\n

\n

Why should we hardcode standards into modules\u2026 if AI can generate them on demand?<\/strong><\/p>\n<\/blockquote>\n\n\n\n

The Shift That Feels Uncomfortable (But Real)<\/h2>\n\n\n\n

This is not about complexity or capability. Terraform modules still work\u2014and work well. But the context has changed.<\/p>\n\n\n\n

We are no longer operating in a world where engineers manually write everything, standardization must be enforced through static abstractions, and refactoring is expensive and slow.<\/p>\n\n\n\n

Today:<\/p>\n\n\n\n

    \n
  • AI can generate Terraform configurations instantly<\/li>\n\n\n\n
  • MCP and provider integrations are already available<\/li>\n\n\n\n
  • Agents can enforce best practices dynamically<\/li>\n\n\n\n
  • Refactoring can be automated at scale<\/li>\n<\/ul>\n\n\n\n

    So the question becomes: Are modules solving a problem that no longer exists in the same way?<\/strong><\/p>\n\n\n\n

    From Modules \u2192 Providers + Intelligence<\/h2>\n\n\n\n

    What I proposed is simple\u2014yet controversial. Instead of:<\/p>\n\n\n\n

    Interface \u2192 Module \u2192 Provider\n<\/code><\/pre>\n\n\n\n
    We move toward:<\/p>\n\n\n\n
    Interface \u2192 Provider (guided by AI)\n<\/code><\/pre>\n\n\n\n
    Your “interface” still exists, but instead of calling a module, it directly interacts with providers, with AI ensuring best practices, security constraints, naming conventions, and resource configurations.<\/p>\n\n\n\n
    In other words: Standardization moves from code\u2026 to intelligence.<\/strong><\/p>\n\n\n\n
    “But My Environment Is a Mess\u2026”<\/h2>\n\n\n\n
    Good. Because this model actually embraces that reality<\/strong>.<\/p>\n\n\n\n
    It doesn’t matter if you have 10 repos or 1,000, each following a different pattern, or naming conventions are inconsistent. We are no longer dependent on manual normalization.<\/p>\n\n\n\n
    Instead: AI agents analyze, apply patterns, refactor continuously, and validate outcomes. The key difference? Your company policies and governance rules live in the agent’s context\u2014not hardcoded in modules. This means policies are enforceable at scale without being a bottleneck. When security or compliance rules change, you update the agent’s guidelines once, and it applies everywhere instantly.<\/p>\n\n\n\n
    The focus shifts from “Is the code standardized?” to “Is the outcome correct and validated?”<\/p>\n\n\n\n
    From an SRE perspective, this aligns perfectly with Error Budget Management<\/strong> and Release Engineering<\/strong>. Rather than investing heavily upfront in perfect module design, you’re allowing controlled variation\u2014validated continuously\u2014and optimizing dynamically.<\/p>\n\n\n\n
    \u26a0\ufe0f The Trade-Off (This Is Important)<\/h2>\n\n\n\n
    This approach does not remove discipline\u2014it shifts it. If before you needed strong module design, now you need strong validation systems.<\/p>\n\n\n\n
    Without that, this becomes chaos. You must have:<\/p>\n\n\n\n
      \n
    • Continuous validation pipelines<\/li>\n\n\n\n
    • Policy enforcement (OPA, checks, guardrails)<\/li>\n\n\n\n
    • Observability over infrastructure<\/li>\n\n\n\n
    • Clear definition of “correct state”<\/li>\n<\/ul>\n\n\n\n
      AI can generate\u2014but you must verify.<\/strong> This is Monitoramento<\/strong> and Automa\u00e7\u00e3o<\/strong> working together\u2014machines generate at scale, humans validate patterns, systems improve continuously.<\/p>\n\n\n\n
      How to Start (Practical Approach)<\/h2>\n\n\n\n
      Don’t rewrite everything. Start small:<\/p>\n\n\n\n
      1. Define Your “Golden Rules”<\/strong> \u2014 Naming conventions, tagging standards, security requirements, cost constraints. These become AI instructions, not module constraints.<\/p>\n\n\n\n
      2. Introduce an AI Layer<\/strong> \u2014 Use agents (Claude Code, etc.), provide structured prompts, connect with providers via MCP or SDKs.<\/p>\n\n\n\n
      3. Add a Validation Loop (Critical)<\/strong> \u2014 Terraform plan checks, policy-as-code, cost estimation, security scans.<\/p>\n\n\n\n
      4. Enable Continuous Refactoring<\/strong> \u2014 Let AI revisit existing code, normalize differences automatically, improve over time instead of enforcing upfront.<\/p>\n\n\n\n
      Final Thought<\/h2>\n\n\n\n
      We are not removing structure. We are relocating where structure lives<\/strong>\u2014from static modules to dynamic intelligence.<\/p>\n\n\n\n
      And maybe the biggest shift is this: Today, suffering with manual standardization is optional.<\/strong><\/p>\n\n\n\n
      Whether we like it or not, AI is no longer a tool\u2014it’s becoming part of your infrastructure architecture.<\/p>\n\n\n\n
      Cheers,<\/p>\n\n\n\n
      Douglas Mugnos<\/p>\n\n\n\n
      MUGNOS-IT \ud83d\ude80<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
      \n\t\t\t\t\t
      \n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"
      There’s something I never thought I would say\u2014but today, I proposed an architecture that challenged one of my own long-standing beliefs. For years, working with large enterprises and global companies, I was one of the main advocates for Terraform standardization through reusable modules. The reasoning was clear: consistency, reusability, governance, and reduced cognitive load. And […]<\/p>","protected":false},"author":3,"featured_media":2847,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2846","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"aioseo_notices":[],"jetpack_featured_media_url":"https:\/\/mugnos-it.com\/wp-content\/uploads\/2026\/05\/ChatGPT-Image-6-de-mai.-de-2026-09_50_20.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/mugnos-it.com\/pt\/wp-json\/wp\/v2\/posts\/2846","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mugnos-it.com\/pt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mugnos-it.com\/pt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mugnos-it.com\/pt\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/mugnos-it.com\/pt\/wp-json\/wp\/v2\/comments?post=2846"}],"version-history":[{"count":4,"href":"https:\/\/mugnos-it.com\/pt\/wp-json\/wp\/v2\/posts\/2846\/revisions"}],"predecessor-version":[{"id":2851,"href":"https:\/\/mugnos-it.com\/pt\/wp-json\/wp\/v2\/posts\/2846\/revisions\/2851"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mugnos-it.com\/pt\/wp-json\/wp\/v2\/media\/2847"}],"wp:attachment":[{"href":"https:\/\/mugnos-it.com\/pt\/wp-json\/wp\/v2\/media?parent=2846"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mugnos-it.com\/pt\/wp-json\/wp\/v2\/categories?post=2846"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mugnos-it.com\/pt\/wp-json\/wp\/v2\/tags?post=2846"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}