Skip to content

Commit a9d7f3c

Browse files
committed
made reviewer edits
1 parent 863afdf commit a9d7f3c

File tree

1 file changed

+10
-6
lines changed

1 file changed

+10
-6
lines changed

articles/iot-edge/how-to-deploy-monitor-vscode.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ If you need to determine which IoT Edge devices you can currently configure, run
125125

126126
## Identify devices with target conditions
127127

128-
To identify the IoT Edge devices that are to receive the deployment, you must specify a target condition. A target condition is met when the condition is met by matching a specified deviceId, tag value, or a reported property value.
128+
To identify the IoT Edge devices that are to receive the deployment, you must specify a target condition. A target condition is met when specified criteria is matched by a deviceId, tag value, or a reported property value.
129129

130130
You configure tags in the device twin. Here is an example of a device twin that has tags:
131131

@@ -149,9 +149,9 @@ Here are some more examples:
149149
* deviceId ='linuxprod1'
150150
* deviceId = 'linuxprod1' OR deviceId = 'linuxprod2' OR deviceId = 'linuxprod3'
151151
* tags.environment ='prod'
152-
* tags.environment = 'prod' AND tags.location = 'westus'
153-
* tags.environment = 'prod' OR tags.location = 'westus'
154-
* tags.operator = 'John' AND tags.environment = 'prod' NOT deviceId = 'linuxprod1'
152+
* tags.environment = 'prod' AND tags.location = 'westus2'
153+
* tags.environment = 'prod' OR tags.location = 'westus2'
154+
* tags.operator = 'John' AND tags.environment = 'prod' AND NOT deviceId = 'linuxprod1'
155155

156156
See [target condition](module-deployment-monitoring.md#target-condition) for details. For more information about device twins and tags, see [Understand and use device twins in IoT Hub](../iot-hub/iot-hub-devguide-device-twins.md).
157157

@@ -205,7 +205,11 @@ After you save the local file, run the **IoT Edge: Update Device Twin** command.
205205

206206
After you have configured the deployment manifest and configured tags in the device twin, you're ready to deploy.
207207

208-
1. From the **View** menu, select **Command Palette** and select the **Azure IoT Edge: Create Deployment at Scale** command. You will be asked for a few parameter values, starting with the **deployment id**.
208+
1. From the **View** menu, select **Command Palette** and select the **Azure IoT Edge: Create Deployment at Scale** command.
209+
210+
1. Navigate to the deployment manifest JSON file that you want to use, and click **Select Edge Deployment Manifest**.
211+
212+
1. Provide values as prompted, starting with the **deployment id**.
209213

210214
![Specify a deployment id](./media/how-to-deploy-monitor-vscode/create-deployment-at-scale.png)
211215

@@ -226,7 +230,7 @@ After you have configured the deployment manifest and configured tags in the dev
226230

227231
## Monitoring and modifying deployments
228232

229-
Use the [Azure CLI](how-to-deploy-monitor-cli.md#monitor-a-deployment) or the [Azure portal](how-to-deploy-monitor.md#monitor-a-deployment) to monitor, modify, and delete deployments. Both provide metrics on your deployments, but the Azure CLI provides additional granularity by allowing you to query values for specific properties.
233+
Use the [Azure CLI](how-to-deploy-monitor-cli.md#monitor-a-deployment) or the [Azure portal](how-to-deploy-monitor.md#monitor-a-deployment) to monitor, modify, and delete deployments. Both provide metrics on your deployments.
230234

231235
## Next steps
232236

0 commit comments

Comments
 (0)