fix prettier errors

Author: sjpb

docs/opentofu-remote-state.md

@@ -6,7 +6,7 @@ This allows deployments to be made from anywhere that can access the state
 without corrupting or conflicting with any existing resources from previous
 deployments.
 
-Using remote state is therefore strongly recommended for  environments which
+Using remote state is therefore strongly recommended for environments which
 should only be instantiated once, e.g. `production` and `staging`.
 
 This page provides guidance for configuring remote states using backends
@@ -31,20 +31,20 @@ but includes some missing details and is modified for common appliance workflows
 
 1. Create the backend file:
 
-    ```shell
-    cp environments/site/tofu/example-backends/gitlab.tf environments/$ENV/tofu
-    ```
+   ```shell
+   cp environments/site/tofu/example-backends/gitlab.tf environments/$ENV/tofu
+   ```
 
 2. Modify `environments/$ENV/tofu/gitlab.tf` to set the default for the
    project ID. This can be found by clicking the 3-dot menu at the top right of
    the GitLab project page.
 
-    ```terraform
-    # environments/$ENV/tofu/backend.tf:
-    terraform {
-        backend "http" {}
-    }
-    ```
+   ```terraform
+   # environments/$ENV/tofu/backend.tf:
+   terraform {
+       backend "http" {}
+   }
+   ```
 
 3. Commit it.
 
@@ -55,12 +55,12 @@ but includes some missing details and is modified for common appliance workflows
 1. Create an access token in the GitLab UI, using either:
 
    a. If project access tokens are available, create one via
-      Project > Settings > Access tokens.
-      The token must have `Maintainer` role and `api` scope.
+   Project > Settings > Access tokens.
+   The token must have `Maintainer` role and `api` scope.
 
    b. Otherwise create a personal access token via
-      User profile > Preferences > Access tokens.
-      The token must have `api` scope.
+   User profile > Preferences > Access tokens.
+   The token must have `api` scope.
 
    Copy the generated secret and set an environment variable:
 
@@ -74,17 +74,17 @@ but includes some missing details and is modified for common appliance workflows
    export TF_VAR_gitlab_username=$your_username
    ```
 
-4. With the environment activated, initialise OpenTofu.
+3. With the environment activated, initialise OpenTofu.
 
-    If no local state exists run:
+   If no local state exists run:
 
-    ```shell
-    cd environments/$ENV/tofu/
-    tofu init
-    ```
-  
-    otherwise append `-migrate-state` to the `init` command to attempt to copy
-    local state to the new backend.
+   ```shell
+   cd environments/$ENV/tofu/
+   tofu init
+   ```
+
+   otherwise append `-migrate-state` to the `init` command to attempt to copy
+   local state to the new backend.
 
 OpenTofu is now configured to use GitLab to store state for this environment.
 
@@ -111,60 +111,61 @@ per-checkout configuration is required.
 
 1. Create an S3 bucket with a name `${cluster_name}-${environment_name}-tfstate`
    where:
-    - `CLUSTER_NAME` is defined in `environments/$ENV/tofu/main.tf`
-    - `$ENVIRONMENT_NAME` is the name of the environment directory
 
-    e.g.
+   - `CLUSTER_NAME` is defined in `environments/$ENV/tofu/main.tf`
+   - `$ENVIRONMENT_NAME` is the name of the environment directory
+
+   e.g.
 
-    ```shell
-    openstack container create research-staging-tfstate
-    ```
+   ```shell
+   openstack container create research-staging-tfstate
+   ```
 
 2. Create `ec2` credentials:
 
-    ```shell
-    openstack ec2 credentials create
-    ```
+   ```shell
+   openstack ec2 credentials create
+   ```
 
-    and make a note of the `access` field returned.
+   and make a note of the `access` field returned.
 
 3. Create the backend file:
 
-    ```shell
-    cp environments/site/tofu/example-backends/s3.tf environments/$ENV/tofu
-    ```
+   ```shell
+   cp environments/site/tofu/example-backends/s3.tf environments/$ENV/tofu
+   ```
 
 4. Modify `environments/$ENV/tofu/s3.tf` to set the default for `s3_backend_endpoint`.
    This is the radosgw address. If not known it can be determined by creating a
    public bucket, and then getting the URL using
-    Project > Containers > (your public bucket) > Link
+   Project > Containers > (your public bucket) > Link
    which provides a URL of the form `https://$ENDPOINT/swift/...`.
 
 5. Add the following to `environments/$ENV/activate`:
 
-    ```bash
-    export AWS_ACCESS_KEY_ID=$EC2_CREDENTIALS_ACCESS
-    export AWS_SECRET_ACCESS_KEY=$(openstack ec2 credentials show $AWS_ACCESS_KEY_ID -f value -c secret)
-    ```
-  
-    replacing `$EC2_CREDENTIALS_ACCESS` with the `access` field of the created
-    credentials.
+   ```bash
+   export AWS_ACCESS_KEY_ID=$EC2_CREDENTIALS_ACCESS
+   export AWS_SECRET_ACCESS_KEY=$(openstack ec2 credentials show $AWS_ACCESS_KEY_ID -f value -c secret)
+   ```
 
-    This avoids these credentials being persisted in local files.
+   replacing `$EC2_CREDENTIALS_ACCESS` with the `access` field of the created
+   credentials.
+
+   This avoids these credentials being persisted in local files.
 
 6. Copy the lines above into your shell to set them for your current shell.
 
 7. With the environment activated, initialise OpenTofu.
 
-    If no local state exists run:
+   If no local state exists run:
+
+   ```shell
+   cd environments/$ENV/tofu/
+   tofu init
+   ```
 
-    ```shell
-    cd environments/$ENV/tofu/
-    tofu init
-    ```
-  
-    otherwise append `-migrate-state` to the `init` command to attempt to copy
-    local state to the new backend.
+   otherwise append `-migrate-state` to the `init` command to attempt to copy
+   local state to the new backend.
 
 8. If this fails, try setting `use_path_style = true` in `environments/$ENV/tofu/s3.tf`.