As tags aren't necessarily immutable, it's probably advisable to use the full hash in most situations anyway.

This is a useful trick in situations where the image changing under your feet isn't very important.

You can have that indirection itself in a data element that does the lookup of the image and returns the digest: https://registry.terraform.io/providers/hashicorp/aws/latest...

So the data element would lookup the tag, and the specific hash is used in the deployment. No funky replace triggers needed.

Sure, you're right in most cases. In the use-case I had, it's a private registry with "immutable" tags (at least enough to stop accidental overwrites - and it is a homelab, so if someone else did it, I'd have worse problems ;))

The point was more about using null_triggers (or `terraform_data` I see) and using the trigger replacement, with the docker resources as purely an illustration.

Not a rails plugin, but earlier this month this was posted to HN :

http://news.ycombinator.com/item?id=3428369

Thats awesome thanks.

I work in a shared office building, and I take a laptop with a self-contained test environment into my day job. I then spend lunch working in a quiet room elsewhere in the building with no internet connection.

It works well for me because I'm awake and thinking about tech problems anyway thanks to the morning, and an hour with no distractions is enough to make small gains.