@@ -97,7 +97,6 @@ export PRINCIPAL_ID=$(az k8s-extension show \
97
97
--name mq \
98
98
--cluster-type connectedClusters \
99
99
--query identity.principalId -o tsv)
100
-
101
100
echo $PRINCIPAL_ID
102
101
```
103
102
@@ -109,7 +108,7 @@ d84481ae-9181-xxxx-xxxx-xxxxxxxxxxxx
109
108
110
109
Then, use Azure CLI to assign publisher and subscriber roles to IoT MQ for the topic space you created.
111
110
112
- Assigning the publisher role:
111
+ Assign the publisher role:
113
112
114
113
``` azurecli
115
114
az role assignment create \
@@ -118,7 +117,7 @@ az role assignment create \
118
117
--scope /subscriptions/$SUBSCRIPTION_ID/resourceGroups/$RESOURCE_GROUP/providers/Microsoft.EventGrid/namespaces/$EVENT_GRID_NAMESPACE/topicSpaces/tutorial
119
118
```
120
119
121
- Assigning the subscriber role:
120
+ Assign the subscriber role:
122
121
123
122
``` azurecli
124
123
az role assignment create \
@@ -135,7 +134,11 @@ az role assignment create \
135
134
Use Azure CLI to get the Event Grid MQTT broker hostname.
136
135
137
136
``` azurecli
138
- az eventgrid namespace show --resource-group $RESOURCE_GROUP --namespace-name $EVENT_GRID_NAMESPACE --query topicSpacesConfiguration.hostname -o tsv
137
+ az eventgrid namespace show \
138
+ --resource-group $RESOURCE_GROUP \
139
+ --namespace-name $EVENT_GRID_NAMESPACE \
140
+ --query topicSpacesConfiguration.hostname \
141
+ -o tsv
139
142
```
140
143
141
144
Take note of the output value for ` topicSpacesConfiguration.hostname ` that is a hostname value that looks like:
0 commit comments