Skip to content

Commit 50c3800

Browse files
Adding get-versions command
1 parent 0cbea31 commit 50c3800

File tree

3 files changed

+24
-11
lines changed

3 files changed

+24
-11
lines changed

articles/iot-operations/deploy-iot-ops/howto-deploy-iot-operations.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -214,8 +214,15 @@ The `check` command displays a warning about missing data flows, which is normal
214214

215215
You can check the configurations of topic maps, QoS, and message routes by adding the `--detail-level 2` parameter to the `check` command for a verbose view.
216216

217+
You can view all versions of the Azure IoT Operations CLI extension that are available by running the following command:
218+
219+
```azurecli
220+
az iot ops get-versions
221+
```
222+
217223
## Next steps
218224

219-
If your components need to connect to Azure endpoints like SQL or Fabric, learn how to [Manage secrets for your Azure IoT Operations deployment](../deploy-iot-ops/howto-manage-secrets.md).
225+
- If your components need to connect to Azure endpoints like SQL or Fabric, learn how to [Manage secrets for your Azure IoT Operations deployment](../deploy-iot-ops/howto-manage-secrets.md).
226+
- To upgrade your Azure IoT Operations deployment to a newer version, see [Upgrade Azure IoT Operations](./howto-upgrade.md).
220227

221228

articles/iot-operations/deploy-iot-ops/howto-deploy-iot-test-operations.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -174,6 +174,12 @@ The `check` command displays a warning about missing data flows, which is normal
174174

175175
You can check the configurations of topic maps, QoS, and message routes by adding the `--detail-level 2` parameter to the `check` command for a verbose view.
176176

177+
You can view all versions of the Azure IoT Operations CLI extension that are available by running the following command:
178+
179+
```azurecli
180+
az iot ops get-versions
181+
```
182+
177183
## Next steps
178184

179185
The Azure IoT Operations instance you deployed is configured for testing scenarios. If you want to enable secure setting and prepare the instance for production scenarios, follow the steps in [Enable secure settings on an existing Azure IoT Operations instance](./howto-enable-secure-settings.md).

articles/iot-operations/deploy-iot-ops/howto-upgrade.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -89,21 +89,21 @@ Use the following steps to upgrade your deployment to the latest version:
8989
az iot ops upgrade --resource-group <RESOURCE_GROUP_NAME> --name <INSTANCE_NAME>
9090
```
9191

92-
1. The CLI outputs a table of the components that have available upgrades. Enter `Y` to continue with the upgrade.
92+
1. The CLI outputs a table of the components that have available upgrades. Enter `Y` to continue with the upgrade.
9393

94-
1. If you want to upgrade to a specific version of Azure IoT Operations that isn't the latest, use the related CLI extension version. Refer to [IoT Operations versions](https://aka.ms/aio-versions) to find the CLI extension version associated with the Azure IoT Operations version that you want and run the following command:
94+
If you want to upgrade to a specific version of Azure IoT Operations that isn't the latest, you can run `az iot ops get-versions` or refer to [IoT Operations versions](https://aka.ms/aio-versions) to find the CLI extension version associated with the Azure IoT Operations version that you want. Get the version number and run the following command to upgrade to that version:
9595

96-
```azurecli
97-
az extension add --upgrade --name azure-iot-ops --version <VERSION_NUMBER>
98-
```
96+
```azurecli
97+
az extension add --upgrade --name azure-iot-ops --version <VERSION_NUMBER>
98+
```
9999

100100
---
101101

102102
## Upgrade to preview version
103103

104104
Sometimes the latest version of Azure IoT Operations is in preview. Check the [Azure IoT Operations versions](https://aka.ms/aio-versions) to see the latest version. During preview releases, version upgrade is blocked, and you need to uninstall Azure IoT Operations and reinstall the preview version.
105105

106-
You can only install a preview version using the Azure CLI. Follow these steps to upgrade to a preview version of Azure IoT Operations:
106+
You can only install a preview version using the Azure CLI.
107107

108108
1. If you have an existing Azure IoT Operations instance, you need to [Uninstall Azure IoT Operations](howto-manage-update-uninstall.md#uninstall) to do a new deployment.
109109
1. Add the latest version of the Azure IoT Operations CLI extension with the `--allow-preview` flag.
@@ -112,11 +112,11 @@ You can only install a preview version using the Azure CLI. Follow these steps t
112112
az extension add --upgrade --name azure-iot-ops --allow-preview
113113
```
114114

115-
1. During preview releases, you can upgrade your deployment to a specific version of Azure IoT Operations by specifying the related CLI extension version. Refer to [IoT Operations versions](https://aka.ms/aio-versions) to find the CLI extension version associated with the Azure IoT Operations version that you want and run the following command:
115+
If you want to upgrade to a specific version of Azure IoT Operations that isn't the latest, you can run `az iot ops get-versions` or refer to [IoT Operations versions](https://aka.ms/aio-versions) to find the CLI extension version associated with the Azure IoT Operations version that you want. Get the version number and run the following command to upgrade to that version:
116116

117-
```azurecli
118-
az extension add --upgrade --name azure-iot-ops --version <VERSION_NUMBER>
119-
```
117+
```azurecli
118+
az extension add --upgrade --name azure-iot-ops --version <VERSION_NUMBER>
119+
```
120120

121121
> [!NOTE]
122122
> In preview releases, the `az iot ops upgrade` command doesn't work for upgrading to a preview version, but it works for configuring the Azure IoT Operations for observability. Add the following parameters to the `upgrade` command:

0 commit comments

Comments
 (0)