Member-only story
Solving Terraform’s Chicken-and-Egg Problem
A step-by-step guide to provisioning and migrating your GCS backend using Terraform
Cloud infrastructure, while massively helpful for scaling up businesses and digitizing processes, has become increasingly complex. That is especially true for the major cloud hyperscalers hyperscalers like Amazon Web Services (AWS) and Google Cloud Platform (GCP).
Even for small teams, it’s usually not an option to manage their cloud resources manually. For example, deploying a serverless Function on GCP might require creating service accounts, custom roles, databases, encryption keys — and that does not even include managing a custom domain.
There are, of course, tools to enable the automation of cloud resource management. So-called Infrastructure as Code (IaC) tools have become the standard for managing cloud resources, because they manage not only the creation but also continuous updates and deletion.
IaC tools, however, also bring some complexity to the table. A tool like Terraform comes with its own static configuration language, while the Terraform competitor Pulumi, for example, favors a more dynamic approach.
