Persist environment variables across quickstarts

Author: kgremban

articles/iot-operations/get-started/quickstart-add-assets.md

@@ -84,10 +84,12 @@ To add an asset endpoint:
 
 These quickstarts use the **OPC PLC simulator** to generate sample data. To enable the quickstart scenario, you need to configure the OPC UA Broker to accept untrusted server certificates and your asset endpoint to connect without mutual trust established. This configuration is not recommended for production or pre-production environments. For more information, see [Deploy the OPC PLC simulator](../manage-devices-assets/howto-configure-opc-plc-simulator.md):
 
+Run the following commands in your Codespaces terminal, which has all of your environment variables configures.
+
 1. To configure the simulator for the quickstart scenario, run the following command:
 
    ```azurecli
-   az k8s-extension update --version 0.3.0-preview --name opc-ua-broker --release-train preview --cluster-name <CLUSTER_NAME> --resource-group <RESOURCE_GROUP> --cluster-type connectedClusters --auto-upgrade-minor-version false --config opcPlcSimulation.deploy=true --config opcPlcSimulation.autoAcceptUntrustedCertificates=true
+   az k8s-extension update --version 0.3.0-preview --name opc-ua-broker --release-train preview --cluster-name $CLUSTER_NAME --resource-group $RESOURCE_GROUP --cluster-type connectedClusters --auto-upgrade-minor-version false --config opcPlcSimulation.deploy=true --config opcPlcSimulation.autoAcceptUntrustedCertificates=true
    ```
 
    > [!CAUTION]
@@ -251,10 +253,10 @@ aio-akri-otel-collector-5c775f745b-g97qv       1/1     Running   3 (4h15m ago)
 aio-akri-agent-daemonset-mp6v7                 1/1     Running   3 (4h15m ago)    2d23h
 ```
 
-On the machine where your Kubernetes cluster is running, run the following command to apply a new configuration for the discovery handler:
+In your Codespaces terminal, run the following command to apply a new configuration for the discovery handler:
 
 ```console
-kubectl apply -f https://raw.githubusercontent.com/Azure-Samples/explore-iot-operations/main/samples/quickstarts/akri-opcua-asset.yaml
+kubectl apply -f /workspaces/explore-iot-operations/samples/quickstarts/akri-opcua-asset.yaml
 ```
 
 The following snippet shows the YAML file that you applied:

articles/iot-operations/get-started/quickstart-deploy.md

@@ -83,30 +83,21 @@ This helper command checks connectivity to Azure Resource Manager and Microsoft
 
 In this section, you use the [az iot ops init](/cli/azure/iot/ops#az-iot-ops-init) command to configure your cluster so that it can communicate securely with your Azure IoT Operations components and key vault, then deploy Azure IoT Operations.
 
-1. Create a key vault. Replace the placeholder parameters with your own information.
+Run the following CLI commands in your Codespaces terminal.
 
-   | Placeholder | Value |
-   | ----------- | ----- |
-   | **RESOURCE_GROUP** | The name of your resource group that contains the connected cluster. |
-   | **KEYVAULT_NAME** | A name for a new key vault. |
+1. Create a key vault. For this scenario, use the same name and resource group as your cluster.
 
    ```azurecli
-   az keyvault create --enable-rbac-authorization false --name $KEYVAULT_NAME --resource-group $RESOURCE_GROUP
+   az keyvault create --enable-rbac-authorization false --name $CLUSTER_NAME --resource-group $RESOURCE_GROUP
    ```
 
    >[!TIP]
    > You can use an existing key vault for your secrets, but verify that the **Permission model** is set to **Vault access policy**. You can check this setting in the Azure portal in the **Access configuration** section of an existing key vault. Or use the [az keyvault show](/cli/azure/keyvault#az-keyvault-show) command to check that `enableRbacAuthorization` is false.
 
-1. Run the following CLI command on your development machine or in your codespace terminal. Replace the placeholder parameters with your own information.
-
-   | Placeholder | Value |
-   | ----------- | ----- |
-   | **CLUSTER_NAME** | The name of your connected cluster. |
-   | **RESOURCE_GROUP** | The name of your resource group that contains the connected cluster. |
-   | **KEYVAULT_NAME** | The name of your key vault. |
+1. Deploy Azure IoT Operations.
 
    ```azurecli
-   az iot ops init --simulate-plc --cluster <CLUSTER_NAME> --resource-group <RESOURCE_GROUP> --kv-id $(az keyvault show --name <KEYVAULT_NAME> -o tsv --query id)
+   az iot ops init --simulate-plc --cluster $CLUSTER_NAME --resource-group $RESOURCE_GROUP --kv-id $(az keyvault show --name $CLUSTER_NAME -o tsv --query id)
    ```
 
    If you get an error that says *Your device is required to be managed to access your resource*, run `az login` again and make sure that you sign in interactively with a browser.

articles/iot-operations/includes/connect-cluster-codespaces.md

@@ -67,6 +67,6 @@ To connect your cluster to Azure Arc:
 
 1. Use the [az connectedk8s enable-features](/cli/azure/connectedk8s#az-connectedk8s-enable-features) command to enable custom location support on your cluster. This command uses the `objectId` of the Microsoft Entra ID application that the Azure Arc service uses.
 
-    ```azurecli
-    az connectedk8s enable-features -n $CLUSTER_NAME -g $RESOURCE_GROUP --custom-locations-oid $OBJECT_ID --features cluster-connect custom-locations
-    ```
+   ```azurecli
+   az connectedk8s enable-features -n $CLUSTER_NAME -g $RESOURCE_GROUP --custom-locations-oid $OBJECT_ID --features cluster-connect custom-locations
+   ```

articles/iot-operations/includes/prepare-codespaces.md

@@ -35,7 +35,9 @@ To get started with your codespace:
    | LOCATION | An Azure region close to you. The following regions are supported in public preview: eastus, eastus2, westus, westus2, westus3, westeurope, or northeurope. |
 
    >[!TIP]
-   > The values you provide as secrets in this step get saved on your GitHub account to be used in this and future codespaces. They're also automatically added as environment variables in the codespace terminal, and you can use those environment variables in the CLI commands in the next section.
+   >The values you provide as secrets in this step get saved on your GitHub account to be used in this and future codespaces. They're also automatically added as environment variables in the codespace terminal, and you can use those environment variables in the CLI commands in the next section.
+   >
+   >Additionally, this codespace automatically creates a `CLUSTER_NAME` environment variable which is set with the codespace name.
 
 1. Select **Create new codespace**.