From a941155d6d20ee883f718fc87b978fd96f674d52 Mon Sep 17 00:00:00 2001
From: Sarah Gibson <drsarahlgibson@gmail.com>
Date: Wed, 29 Jan 2025 11:59:42 +0000
Subject: [PATCH] Remove discussion of terraform backends from docs

---
 .../new-cluster/new-cluster.md                | 15 +---------
 docs/topic/infrastructure/terraform.md        | 30 +------------------
 2 files changed, 2 insertions(+), 43 deletions(-)

diff --git a/docs/hub-deployment-guide/new-cluster/new-cluster.md b/docs/hub-deployment-guide/new-cluster/new-cluster.md
index 65aa93993e..9791f8ace3 100644
--- a/docs/hub-deployment-guide/new-cluster/new-cluster.md
+++ b/docs/hub-deployment-guide/new-cluster/new-cluster.md
@@ -333,7 +333,7 @@ terraform init
 :sync: gcp-key
 ```bash
 cd terraform/gcp
-terraform init -backend-config=backends/default-backend.hcl -reconfigure
+terraform init
 ```
 ````
 
@@ -346,19 +346,6 @@ terraform init
 ````
 `````
 
-````{note}
-There are other backend config files stored in `terraform/backends` that will configure a different storage bucket to read/write the remote terraform state for projects which we cannot access from GCP with our `@2i2c.org` email accounts.
-This saves us the pain of having to handle multiple authentications as these storage buckets are within the project we are trying to deploy to.
-
-For example, to work with Pangeo you would initialise terraform like so:
-
-```bash
-terraform init -backend-config=pangeo-backend.hcl -reconfigure
-```
-
-<!-- TODO: add instructions on how/when to create other backends -->
-````
-
 ## Creating a new terraform workspace
 
 We use terraform workspaces so that the state of one `.tfvars` file does not influence another.
diff --git a/docs/topic/infrastructure/terraform.md b/docs/topic/infrastructure/terraform.md
index 342e2f48b0..92f8d7fd34 100644
--- a/docs/topic/infrastructure/terraform.md
+++ b/docs/topic/infrastructure/terraform.md
@@ -35,17 +35,6 @@ cd terraform/azure
 terraform init
 ```
 
-````{note}
-Currently, since our GCP terraform config is the only one that uses different backends, an extra `-backend-config` flag needs to be passed to the `init` command to initialize.
-
-For example, for our Pangeo projects, run:
-
-```bash
-cd terraform/gcp
-terraform init -backend-config=backends/pangeo-backend.hcl
-```
-````
-
 ```{note}
 If prior backend data exists in a `terraform.lock.hcl`, you might see an `Error: Backend configuration changed` when trying to initialize that backend. To reconfigure this backend, ignoring any saved configuration, add the `-reconfigure` flag to the init command.
 ```
@@ -92,23 +81,6 @@ terraform workspace select justiceinnovationlab
 For the majority of day-to-day work, this will be the prevalent workflow provided you have initialised terraform with
 
 ```bash
-terraform init -backend-config=backends/default-backend.hcl -reconfigure
+terraform init
 ```
 ````
-
-### If the new workspace is stored in a different backend to the current workspace
-
-To change between workspaces that are stored in _different_ backends, terraform will need to be reinitialised in order to pick up the new backend.
-The commands, therefore, are:
-
-```bash
-terraform init -backend-config=backends/<REQUIRED_CONFIG>.hcl -reconfigure
-terraform workspace select WORKSPACE_NAME
-```
-
-For example, if you were working on our `pilot-hubs`, with our default backend initialised, but wanted to change to working on our Pangeo deployments, the commands would look as follows:
-
-```bash
-terraform init -backend-config=backends/pangeo-backend.hcl -reconfigure
-terraform workspace select pangeo-hubs
-```