<?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 Pi Stack</title><link>https://www.pistack.xyz/tags/terraform/</link><description>Recent content in Terraform on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 22 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/terraform/index.xml" rel="self" type="application/rss+xml"/><item><title>Self-Hosted Infrastructure Drift Detection: Driftctl, Cloud Custodian &amp; OpenTofu Guide 2026</title><link>https://www.pistack.xyz/posts/self-hosted-infrastructure-drift-detection-driftctl-cloud-custodian-opentofu-guide-2026/</link><pubDate>Wed, 22 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/self-hosted-infrastructure-drift-detection-driftctl-cloud-custodian-opentofu-guide-2026/</guid><description>&lt;h2 id="why-infrastructure-drift-detection-matters">Why Infrastructure Drift Detection Matters&lt;/h2>
&lt;p>Infrastructure as Code (IaC) tools like Terraform and OpenTofu let you define cloud resources declaratively. But in practice, your real-world infrastructure almost always diverges from your code. Someone makes a manual change in the AWS console, a security team patches a security group, an autoscaler launches instances outside your Terraform state, or a team member deletes a resource directly. These are all examples of &lt;strong>infrastructure drift&lt;/strong> — the gap between what your IaC says should exist and what actually exists in your cloud environment.&lt;/p></description></item></channel></rss>