Twitxy Saved

Gordon Murray

Verified account This account is verified. Learn more

@gortron

Creator of Firn: vector + full-text search on object storage. Platform & data infra engineer. AWS, Terraform, Flink. AWS Solutions Architect.
Cork, Ireland gordonmurray.ie Joined March 2007
1.1K Following 1.4K Followers 14K Posts

Latest posts 5

Pinned post

Gordon Murray Verified account @gortron
Firn has a Python package now!

Just `pip install firn`

Vector and full-text search on object storage, straight from Python. The engine embeds in-process, so there's no server: point it at a local folder or an S3 bucket.

Imagine how happy your SysOps team will be with no cluster to manage. Or your CFO, with no managed solution to approve
0 replies 2 reposts 31 likes 1.9K views View on X
Gordon Murray Verified account @gortron
I ran into this with a Paperclip experiment I ran: a concurrent-scan test could miss incorrect output.

Independent review caught it tough along with claims the evidence didn’t support.
The tests themselves needed checking

gordonmurray.ie/data/2026/10/2…
Dominik Tornow Verified account @DominikTornow 3d
AWS Emulator is a cool project, but notice the language in the article: Agent reviewers are called gates, agent-written tests are called guardrails.

Degrading the meaning of the terms to the equivalent of "make no mistakes".

x.com/amazon/status/…
View quoted post on X
Gordon Murray Verified account @gortron
Clear read-only checks are useful. I built Out of State for a related question: which AWS resources have no match in the Terraform states I supply?

It distinguishes missing matches from incomplete scans. It doesn’t check configuration drift.

github.com/gordonmurray/o…
github.com GitHub - gordonmurray/outofstate.dev: Find what's running outside your Terraform code. A CLI that... Find what's running outside your Terraform code. A CLI that compares the resources in your AWS accounts with your Terraform states and reports back - gordonmurray/outofstate.dev
Guptha Gudivada | DevOps & SRE Verified account @Guptha_Gudivada 3d
Terraform needs a dedicated drift detection command.

And there's an interesting debate happening around this.

Today, teams can use:

terraform plan -refresh-only -detailed-exitcode

But should infrastructure drift detection have its own command?

Imagine having:

terraform drift

A dedicated command that:
→ Checks infrastructure for out-of-band changes.
→ Is guaranteed to be read-only.
→ Returns clear drift-specific exit codes.
→ Can safely run in scheduled CI/CD checks.

There's an open feature request for this in HashiCorp's Terraform repository.

A Terraform maintainer has raised an interesting counterpoint:

The existing plan functionality already detects drift. Do we really need another command?

Personally, I like the idea of explicit read-only operations in infrastructure automation.

Less ambiguity. Fewer opportunities for accidental changes.

But I want to hear from people running Terraform at scale.

Would you prefer:

A) A dedicated terraform drift command

B) Existing terraform plan + refresh-only + JSON parsing

Which approach would you trust more in production?
View quoted post on X
Gordon Murray Verified account @gortron
I made a thing this weekend: outofstate.dev

It lists the AWS resources that aren't in your Terraform state yet. RDS, load balancers, S3, Lambda and NAT gateways so far.
An agent could do this too, but this way you don't burn a pile of tokens on it. And it isn't Rust, its Go!
outofstate.dev Out of State Find what's running outside your Terraform. A local, read-only CLI for AWS and Terraform.