Skip to content

Commit 89b1851

Browse files
committed
Split commands
1 parent 9676af7 commit 89b1851

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

articles/iot-operations/connect-to-cloud/tutorial-connect-event-grid.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,6 @@ export PRINCIPAL_ID=$(az k8s-extension show \
9797
--name mq \
9898
--cluster-type connectedClusters \
9999
--query identity.principalId -o tsv)
100-
101100
echo $PRINCIPAL_ID
102101
```
103102

@@ -109,7 +108,7 @@ d84481ae-9181-xxxx-xxxx-xxxxxxxxxxxx
109108

110109
Then, use Azure CLI to assign publisher and subscriber roles to IoT MQ for the topic space you created.
111110

112-
Assigning the publisher role:
111+
Assign the publisher role:
113112

114113
```azurecli
115114
az role assignment create \
@@ -118,7 +117,7 @@ az role assignment create \
118117
--scope /subscriptions/$SUBSCRIPTION_ID/resourceGroups/$RESOURCE_GROUP/providers/Microsoft.EventGrid/namespaces/$EVENT_GRID_NAMESPACE/topicSpaces/tutorial
119118
```
120119

121-
Assigning the subscriber role:
120+
Assign the subscriber role:
122121

123122
```azurecli
124123
az role assignment create \
@@ -135,7 +134,11 @@ az role assignment create \
135134
Use Azure CLI to get the Event Grid MQTT broker hostname.
136135

137136
```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
139142
```
140143

141144
Take note of the output value for `topicSpacesConfiguration.hostname` that is a hostname value that looks like:

0 commit comments

Comments
 (0)