Skip to content
Permalink
Browse files

post on automated devops

  • Loading branch information...
aaronpowell committed Jul 23, 2019
1 parent 9adaf97 commit c5cd7d7234f9c14d9a8763d9c665f8c1ec2b50ce
@@ -206,7 +206,7 @@ With our Image built we can push it to our container registry, again to support

For us to deploy the image we won't use the `iotedgedev` tool, instead we'll use the [Azure CLI](https://docs.microsoft.com/en-us/cli/azure?{{< cda >}}) and specifically the [IoT Extensions](https://github.com/azure/azure-iot-cli-extension), so grab the Azure CLI (I use the Docker distribution of it), log in to your account and install the IoT Extension.

We're going to use the [`edge deployment create`](https://docs.microsoft.com/en-us/cli/azure/ext/azure-cli-iot-ext/iot/edge/deployment?view=azure-cli-latest#ext-azure-cli-iot-ext-az-iot-edge-deployment-create?{{< cda >}}) command to create a deployment in IoT Hub for our IoT Edge device using the deployment template we specified above.
We're going to use the [`edge deployment create`](https://docs.microsoft.com/en-us/cli/azure/ext/azure-cli-iot-ext/iot/edge/deployment?view=azure-cli-latest&{{< cda >}}#ext-azure-cli-iot-ext-az-iot-edge-deployment-create) command to create a deployment in IoT Hub for our IoT Edge device using the deployment template we specified above.

```sh
$> az iot edge deployment create --deployment-id deployment-01 --hub-name <iot hub name in Azure> --content <path to deployment JSON file> --target-condition deviceId='<name of IoT device in Azure>' --priority 0

Large diffs are not rendered by default.

Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.

0 comments on commit c5cd7d7

Please sign in to comment.
You can’t perform that action at this time.