Tag: google-cloud
All the articles with the tag "google-cloud".
I Could See Every Resource. I Still Could Not Rebuild It.
Taking over cloud infrastructure someone else built, and why a read-only inventory answers the easy question rather than the one that decides the handover.
Our Worst Terraform Deploy Took 71 Minutes. The Fix Was One Flag.
Finding it meant ignoring the median, and controlling for the thing that made my first comparison lie.
One Shared Service Account Would Have Been 200 Lines Shorter
A generated graph of 131 services can share one identity or carry 131 of them. The second costs 216 IAM bindings, and it is the only version where a leaked credential is survivable.
Every Deploy Reported Success. The Endpoint Had Been Unreachable for Two Weeks.
A 404 is not one thing, and the difference between text/plain, text/html and application/json was the entire diagnosis.
Two Environments, One Resource. The Label Said 'dev'. The Name Said Otherwise.
Adding multi-environment support to a platform that names its resources by service, and the collision that every successful deploy silently confirmed.
Delete the State File. Redeploy. Nothing Should Happen.
How generated Terraform learns to adopt infrastructure it did not create, and the three ways a cloud inventory lies about what things are called.
Terraform Created the Service. The Image Did Not Exist Yet.
Generated infrastructure creates services before their containers exist, and a moving tag makes rollback a guess. Two fixes: read the live image before you write it, and pin to a digest.
Building an Internal Developer Platform That Deploys Into Someone Else's Cloud
Multi-tenant infrastructure generation, and the three design decisions that turned out to matter most.