<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Driftctl on SRE Engineering Practice</title><link>https://www.sre.wang/en/tags/driftctl/</link><description>Recent content in Driftctl on SRE Engineering Practice</description><image><title>SRE Engineering Practice</title><url>https://www.sre.wang/share-card-square.jpg</url><link>https://www.sre.wang/share-card-square.jpg</link></image><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 23 Oct 2026 00:37:42 +0800</lastBuildDate><atom:link href="https://www.sre.wang/en/tags/driftctl/index.xml" rel="self" type="application/rss+xml"/><item><title>3 Untracked Resources at 2 AM: 6 Engineering Decisions for Terraform Drift Detection and Remediation</title><link>https://www.sre.wang/en/posts/terraform-drift-detection-remediation/</link><pubDate>Fri, 23 Oct 2026 00:37:42 +0800</pubDate><guid>https://www.sre.wang/en/posts/terraform-drift-detection-remediation/</guid><description>Your Terraform state says everything is fine, but production has an untracked security group — configuration drift is the biggest blind spot in IaC. This article covers the three drift types (Emergent/Pseudo/Introduced), terraform plan -detailed-exitcode detection, driftctl/Snyk IaC comparison, embedding drift detection in CI/CD pipelines, three remediation strategies (reconcile/import/rebuild), 6 production pitfalls, and a drift governance framework with HCP Terraform vs self-hosted selection guidance.</description></item></channel></rss>