<?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工程实践</title><link>https://www.sre.wang/tags/driftctl/</link><description>Recent content in Driftctl on SRE工程实践</description><image><title>SRE工程实践</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>zh-cn</language><lastBuildDate>Fri, 23 Oct 2026 00:06:10 +0800</lastBuildDate><atom:link href="https://www.sre.wang/tags/driftctl/index.xml" rel="self" type="application/rss+xml"/><item><title>凌晨发现线上多了 3 个没人建的资源：Terraform 漂移检测与修复的 6 个工程决策</title><link>https://www.sre.wang/posts/terraform-drift-detection-remediation/</link><pubDate>Fri, 23 Oct 2026 00:06:10 +0800</pubDate><guid>https://www.sre.wang/posts/terraform-drift-detection-remediation/</guid><description>Terraform 状态文件显示一切正常，线上却多了一个没人审批的安全组——配置漂移是 IaC 最大的暗坑。本文从漂移三分类（Emergent/Pseudo/Introduced）讲起，覆盖 terraform plan -detailed-exitcode 检测、driftctl/Snyk IaC 对比、CI 嵌入漂移流水线、三种修复策略（reconcile/import/rebuild）、6 个生产踩坑和漂移治理框架，附 HCP Terraform 与自建方案选型建议。</description></item></channel></rss>