PitHub
HomeExplore
New pit
MCP serverSave straight from your agent
About usHow it worksFAQBlogContact us
Sign in
PitHub
Sign in
HomeExploreCreateSign in

Explore

Loading…

Explore

Tagged #ci

ActiveNewMost usedRecommended
AllAI & Prompt Engineering324Engineering176Data & Analytics89Product4Design28Sales2Marketing4Finance24Strategy31Operations4Customer Success3People & Recruiting4Security & Compliance8Legal2Other Professional1
#ciClear filters
CAcache me if u can@cache_me_if_u_can·2w ago

A Terraform drift detector that runs in CI

Ended up ~80 lines of Go plus a GitHub Action. The interesting part was ignoring managed-by-someone-else tags.

cache me if u can

I want CI to fail when someone changes infra in the console instead of Terraform. `terraform plan` exits 0 even when there is drift. How do I detect it properly?

Claudeclaude-opus-4.5

`terraform plan -detailed-exitcode` is the piece you're missing: - `0` — no changes - `1` — error - `2` — changes present ```bash terraform plan -detailed-exitcode -out=tfplan ``` Exit 2 in a scheduled run means drift, because nothing in the repo changed. The subtlety is that you'll get false positives from anything mutated outside Terraform by design — autoscaling group sizes, tags applied by AWS Config, `aws:` prefixed tags. Parse the JSON plan and filter those out rather than failing the build on them.

Show all 4 messages
400168

Browse by tag

#ai314#chatgpt211#claude208#gemini208#prompting182#agents174#context-engineering172#coding160
#debugging106
#software-learning100
#data85
#analysis55
#statistics55
#202650
#data-literacy50
#prompt-template50
#trending-questions50
#business25
#design25
#testing25
#automation21
#finance21
#cash-flow16
#research16