This folder provides the necessary infrastructure for the acceptance tests in this backend. In order to use this, you must have administrative privileges within your Azure Subscription.

We recommend using CLI authentication and setting the subscription using the ARM_SUBSCRIPTION_ID environment variable:

```bash
$ az login
$ export ARM_SUBSCRIPTION_ID="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
```

Once those are set, you can initialize and apply the OpenTofu workspace:

```bash
$ tofu init
$ tofu apply
# When you're ready to obtain the secrets through environment variables
$ tofu apply -show-sensitive
```

You should see some environment variables that look like this:

```bash
export TF_AZURE_TEST_CLIENT_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
export TF_AZURE_TEST_CLIENT_SECRET=some~secret~string
```

Copy and paste these into the command line to provide the secrets for the backend tests.

A file called `certs.pfx` should also be created, which can be placed in an appropriate directory and used for certificate authentication by setting the path appropriately, perhaps something like:

```bash
export TF_AZURE_TEST_CERT_PATH="meta-test/certs.pfx"
export TF_AZURE_TEST_CERT_PASSWORD=SoMePaSsWoRd
```

### Managed Service Identity

By default, the virtual machine, identity, and associated authorizations required for MSI testing are not set up by this workspace. In order to set those up, you need some extra variables:

```bash
$ tofu apply -show-sensitive -var 'use_msi=true' -var 'location=centralus' -var 'ssh_pub_key_path=~/.ssh/id_rsa.pub'
```

The last two variables are optional; the defaults have been provided here. After running this, some additional environment variables will be available.

Additionally, there should be a small output with the ssh instructions, and the IP address of the VM:

```bash
ssh_instructions = "ssh azureadmin@xxx.xxx.xxx.xxx"
```

In order to tear down msi infrastructure, while keeping the rest of the credentials and setup, simply run the `tofu apply` without the `use_msi=true` variable.

### AKS Workload Identity

By default, the Kubernetes cluster, identity, and associated authorizations required for AKS Workload Identity testing are not set up by this workspace. In order to set those up, you need some extra variables:

```bash
$ tofu apply -show-sensitive -var 'use_aks_workload_identity=true' -var 'location=centralus'
```

There are additional instructions listed under `aks_kubectl_instructions`. It should look something like this:

```bash
az aks get-credentials --name "azClusterTestabcd" --resource-group "acctestRG-backend-xxxx-abcd"
cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: ServiceAccount
metadata:
  annotations:
    azure.workload.identity/client-id: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
  name: "workload-identity-abcd"
  namespace: "default"
---
apiVersion: v1
kind: Pod
metadata:
  name: shell-demo
  namespace: default
  labels:
    azure.workload.identity/use: "true"
spec:
  serviceAccountName: "workload-identity-abcd"
  volumes:
  - name: shared-data
    emptyDir: {}
  containers:
  - name: nginx
    image: nginx
    volumeMounts:
    - name: shared-data
      mountPath: /usr/share/nginx/html
  hostNetwork: true
  dnsPolicy: Default
EOF
```

Copying and pasting this into the shell will authenticate into the newly-created kubernetes cluster and create a service account and pod. This pod will be the workload the test will be running in.

In order to tear down Kubernetes cluster infrastructure, while keeping the rest of the credentials and setup, simply run the `tofu apply` without the `use_aks_workload_identity=true` variable.

### Customer Managed Keys

By default, the Key Vault, encryption key, and encryption scope required for CMK testing are not set up by this workspace. In order to set those up, you need an extra variable:

```bash
$ tofu apply -show-sensitive -var 'use_cmk=true' -var 'location=centralus'
```

The location variable is optional; the default has been provided here. After running this, the CMK environment variables will be available. You can get them under `cmk_env_vars`.

```bash
$ tofu output cmk_env_vars -show-sensitive
```

Copy and paste these into the command line to provide the secrets for the CMK backend tests.

In order to tear down CMK infrastructure, while keeping the rest of the credentials and setup, simply run `tofu apply` without the `use_cmk=true` variable.

### Cleanup

Simply run

```bash
$ tofu destroy
```

... and all the test infrastructure will be deleted.
