<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>terraform on Platform Engineering and Authentication</title>
    <link>https://codepurrpurr.io/tags/terraform/</link>
    <description>Recent content in terraform on Platform Engineering and Authentication</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&lt;a href=&#34;https://creativecommons.org/licenses/by-nc/4.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CC BY-NC 4.0&lt;/a&gt;</copyright>
    <lastBuildDate>Sun, 08 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://codepurrpurr.io/tags/terraform/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Layering Terraform for Platform Interfaces</title>
      <link>https://codepurrpurr.io/platform-engineering/layering-terraform-platform-interfaces/</link>
      <pubDate>Sun, 08 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://codepurrpurr.io/platform-engineering/layering-terraform-platform-interfaces/</guid>
      <description>Problem Terraform is often treated as a direct infrastructure authoring tool.
Even with modules, consumers still think in VPCs, subnets, AMIs, security groups, listeners, and target groups.
That is not a platform interface.
A platform interface should let consumers describe service intent.
The platform should resolve topology, implementation, and provider behavior internally.
The goal is not to hide every infrastructure decision. Network sizing can still be a valid service-level parameter.</description>
    </item>
    
  </channel>
</rss>
