The day-two work that keeps a mature org running: editing state without breaking it, walking the google provider across major versions, replacing live resources without dropping traffic, recovering after state loss, debugging GCP's asynchronous propagation, and standing the whole org up on Cloud Foundation Fabric / FAST.
6 topics
Everything before this chapter built infrastructure; this chapter keeps it alive. The Hatch org is past greenfield — a real hierarchy of folders, a fleet of state files in hatch-tfstate, and live resources that bill money and serve traffic. The operations that matter now are the ones you run while the system is in production, where a wrong command is not a failed plan but an outage or a wiped database.
Six topics cover that surface. State surgery and its safer declarative replacements. Upgrading the google provider across dozens of stacks without a week of firefighting. Replacing resources with zero downtime. Disaster recovery when state is corrupted or gone. Debugging the propagation and eventual-consistency failures that define Terraform-on-GCP. And, last, building the org's whole foundation with Cloud Foundation Fabric and FAST instead of hand-assembling it from primitives.