Skip to content

Commit 41ff1e7

Browse files
authored
Merge pull request #290443 from asergaz/sergaz-enabless-ga
Fix variable naming for secure settings in Azure CLI examples
2 parents 7eb2525 + c97bdbb commit 41ff1e7

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/iot-operations/deploy-iot-ops/howto-enable-secure-settings.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ To set up secrets management:
112112

113113
```azurecli
114114
# Variable block
115-
INSTANCE_NAME="<INSTANCE_NAME>"
115+
AIO_INSTANCE_NAME="<AIO_INSTANCE_NAME>"
116116
RESOURCE_GROUP="<RESOURCE_GROUP>"
117117
USER_ASSIGNED_MI_NAME="<USER_ASSIGNED_MI_NAME>"
118118
KEYVAULT_NAME="<KEYVAULT_NAME>"
@@ -124,7 +124,7 @@ To set up secrets management:
124124
KEYVAULT_RESOURCE_ID=$(az keyvault show --name $KEYVAULT_NAME --resource-group $RESOURCE_GROUP --query id --output tsv)
125125
126126
#Enable secret synchronization
127-
az iot ops secretsync enable --name $INSTANCE_NAME \
127+
az iot ops secretsync enable --instance $AIO_INSTANCE_NAME \
128128
--resource-group $RESOURCE_GROUP \
129129
--mi-user-assigned $USER_ASSIGNED_MI_RESOURCE_ID \
130130
--kv-resource-id $KEYVAULT_RESOURCE_ID
@@ -134,7 +134,7 @@ To set up secrets management:
134134
135135
```azurecli
136136
# Variable block
137-
INSTANCE_NAME="<INSTANCE_NAME>"
137+
AIO_INSTANCE_NAME="<AIO_INSTANCE_NAME>"
138138
$RESOURCE_GROUP="<RESOURCE_GROUP>"
139139
$USER_ASSIGNED_MI_NAME="<USER_ASSIGNED_MI_NAME>"
140140
$KEYVAULT_NAME="<KEYVAULT_NAME>"
@@ -146,7 +146,7 @@ To set up secrets management:
146146
$KEYVAULT_RESOURCE_ID=$(az keyvault show --name $KEYVAULT_NAME --resource-group $RESOURCE_GROUP --query id --output tsv)
147147
148148
# Enable secret synchronization
149-
az iot ops secretsync enable --name $INSTANCE_NAME `
149+
az iot ops secretsync enable --instance $AIO_INSTANCE_NAME `
150150
--resource-group $RESOURCE_GROUP `
151151
--mi-user-assigned $USER_ASSIGNED_MI_RESOURCE_ID `
152152
--kv-resource-id $KEYVAULT_RESOURCE_ID
@@ -171,15 +171,15 @@ Some Azure IoT Operations components, like dataflow endpoints, use a user-assign
171171
172172
```azurecli
173173
# Variable block
174-
INSTANCE_NAME="<INSTANCE_NAME>"
174+
AIO_INSTANCE_NAME="<AIO_INSTANCE_NAME>"
175175
RESOURCE_GROUP="<RESOURCE_GROUP>"
176176
USER_ASSIGNED_MI_NAME="<USER_ASSIGNED_MI_NAME FOR CLOUD CONNECTIONS>"
177177
178178
#Get the resource ID of the user-assigned managed identity
179179
USER_ASSIGNED_MI_RESOURCE_ID=$(az identity show --name $USER_ASSIGNED_MI_NAME --resource-group $RESOURCE_GROUP --query id --output tsv)
180180
181181
#Assign the identity to the Azure IoT Operations instance
182-
az iot ops identity assign --name $INSTANCE_NAME \
182+
az iot ops identity assign --name $AIO_INSTANCE_NAME \
183183
--resource-group $RESOURCE_GROUP \
184184
--mi-user-assigned $USER_ASSIGNED_MI_RESOURCE_ID
185185
```
@@ -188,7 +188,7 @@ Some Azure IoT Operations components, like dataflow endpoints, use a user-assign
188188
189189
```azurecli
190190
# Variable block
191-
$INSTANCE_NAME="<INSTANCE_NAME>"
191+
$AIO_INSTANCE_NAME="<AIO_INSTANCE_NAME>"
192192
$RESOURCE_GROUP="<RESOURCE_GROUP>"
193193
$USER_ASSIGNED_MI_NAME="<USER_ASSIGNED_MI_NAME FOR CLOUD CONNECTIONS>"
194194
@@ -197,7 +197,7 @@ Some Azure IoT Operations components, like dataflow endpoints, use a user-assign
197197
198198
199199
# Assign the identity to the Azure IoT Operations instance
200-
az iot ops identity assign --name $INSTANCE_NAME `
200+
az iot ops identity assign --name $AIO_INSTANCE_NAME `
201201
--resource-group $RESOURCE_GROUP `
202202
--mi-user-assigned $USER_ASSIGNED_MI_RESOURCE_ID
203203
```

0 commit comments

Comments
 (0)