You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-operations/includes/connect-cluster.md
+8-11Lines changed: 8 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,29 +23,23 @@ To connect your cluster to Azure Arc:
23
23
> * Open the codespace in VS Code desktop, and then return to the browser terminal and rerun `az login`.
24
24
> * Or, after you get the localhost error on the browser, copy the URL from the browser and run `curl "<URL>"` in a new terminal tab. You should see a JSON response with the message "You have logged into Microsoft Azure!."
25
25
26
-
1. Set an environment variable for the cluster name as it will show up in your resource group.
26
+
1. Set environment variables for your Azure subscription, location, a new resource group, and the cluster name as it will show up in your resource group.
27
27
28
-
```bash
29
-
# Name of the Arc-enabled cluster to create in your resource group
30
-
export CLUSTER_NAME=<NEW_CLUSTER_NAME>
31
-
```
32
-
33
-
1. Set environment variables for your Azure subscription, location, and a new resource group. If you're using GitHub Codespaces and set these secrets when creating your codespace, you can skip this step.
28
+
If you're using GitHub Codespaces and set up these values as recommended secrets when creating your codespace, skip this step. The codespace automatically sets the cluster name to be the same as the codespace name.
34
29
35
30
```bash
36
31
# Id of the subscription where your resource group and Arc-enabled cluster will be created
37
32
export SUBSCRIPTION_ID=<SUBSCRIPTION_ID>
38
-
```
39
33
40
-
```bash
41
34
# Azure region where the created resource group will be located
42
35
# Currently supported regions: "eastus", "eastus2", "westus", "westus2", "westus3", "westeurope", or "northeurope"
43
36
export LOCATION=<REGION>
44
-
```
45
37
46
-
```bash
47
38
# Name of a new resource group to create which will hold the Arc-enabled cluster and Azure IoT Operations resources
48
39
export RESOURCE_GROUP=<NEW_RESOURCE_GROUP_NAME>
40
+
41
+
# Name of the Arc-enabled cluster to create in your resource group
42
+
export CLUSTER_NAME=<NEW_CLUSTER_NAME>
49
43
```
50
44
51
45
1. Set the Azure subscription context for all commands:
@@ -56,6 +50,9 @@ To connect your cluster to Azure Arc:
56
50
57
51
1. Register the required resource providers in your subscription:
58
52
53
+
>[!NOTE]
54
+
>This step only needs to be run once per subscription.
55
+
59
56
```azurecli
60
57
az provider register -n "Microsoft.ExtendedLocation"
Copy file name to clipboardExpand all lines: articles/iot-operations/includes/prepare-codespaces.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,14 +26,17 @@ To get started with your codespace:
26
26
27
27
[](https://codespaces.new/Azure-Samples/explore-iot-operations?quickstart=1)
28
28
29
-
You don't have to provide the recommended secrets at this step. If you do, they get saved on your GitHub account to be used in this and future codespaces. They're also added as environment variables in the codespace terminal, and you don't have to run the CLI commands in the next section that configure the subscription, resource group, or location variables.
29
+
1. Provide the following recommended secrets for your codespace:
30
30
31
31
| Parameter | Value |
32
32
| --------- | ----- |
33
33
| SUBSCRIPTION_ID | Your Azure subscription ID. |
34
34
| RESOURCE_GROUP | A name for a new Azure resource group where your cluster will be created. |
35
35
| LOCATION | An Azure region close to you. The following regions are supported in public preview: eastus, eastus2, westus, westus2, westus3, westeurope, or northeurope. |
36
36
37
+
>[!TIP]
38
+
> 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.
39
+
37
40
1. Select **Create new codespace**.
38
41
39
42
1. Once the codespace is ready, select the menu button at the top left, then select **Open in VS Code Desktop**.
0 commit comments