Skip to content

Commit 1e10b2f

Browse files
Removing --enable-rsync in create command.
1 parent 0ab5fce commit 1e10b2f

File tree

3 files changed

+11
-7
lines changed

3 files changed

+11
-7
lines changed

articles/iot-operations/deploy-iot-ops/howto-manage-update-uninstall.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -202,7 +202,7 @@ In general, Azure IoT Operations uses the Azure Arc platform to provide a hybrid
202202
However, you can also manage the components of Azure IoT Operations using YAML Kubernetes deployment manifests. This means you can use tools like `kubectl` to manage some components of Azure IoT Operations. This feature is in preview and has some limitations:
203203

204204
- Only some components support using Kubernetes deployment manifests. These components are the [MQTT broker](../manage-mqtt-broker/overview-broker.md) and [data flows](../connect-to-cloud/overview-dataflow.md). Other components like the connector for OPC UA and Akri services don't support this feature.
205-
- Unless Azure IoT Operations is [deployed with resource sync enabled using `az iot ops create --enable-rsync`](/cli/azure/iot/ops#az-iot-ops-create), changes made to the resources using Kubernetes deployment manifests are not synced to Azure. To learn more about resource sync, see [Resource sync](/azure/azure-arc/data/resource-sync).
205+
- Unless Azure IoT Operations is [deployed with resource sync enabled using `az iot ops rsync enable`](/cli/azure/iot/ops#az-iot-ops-rsync), changes made to the resources using Kubernetes deployment manifests are not synced to Azure. To learn more about resource sync, see [Resource sync](/azure/azure-arc/data/resource-sync).
206206
- Even if resource sync is enabled, brand new resources created using Kubernetes deployment manifests are not synced to Azure. Only changes to existing resources are synced.
207207

208208
## Uninstall

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ The following table describes Azure IoT Operations deployment and management tas
7272
| Register resource providers | Microsoft.ExtendedLocation/register/action Microsoft.SecretSyncController/register/action Microsoft.Kubernetes/register/action Microsoft.KubernetesConfiguration/register/action Microsoft.IoTOperations/register/action Microsoft.DeviceRegistry/register/action| Only required to do once per subscription. |
7373
| Create a schema registry. | **Microsoft.Authorization/roleAssignments/write** permissions at the resource group level. | |
7474
| Create secrets in Key Vault | **Key Vault Secrets Officer** role at the resource level. | Only required for secure settings deployment. |
75-
| Enable resource sync rules on an Azure IoT Operations instance | **Microsoft.Authorization/roleAssignments/write** permissions at the resource group level. | Resource sync rules are disabled by default, but can be enabled as part of the [az iot ops create](/cli/azure/iot/ops#az-iot-ops-create) command. |
75+
| Enable resource sync rules on an Azure IoT Operations instance | **Microsoft.Authorization/roleAssignments/write** permissions at the resource group level. | Resource sync rules are disabled by default, but can be enabled as part of the [az iot ops rsync](/cli/azure/iot/ops#az-iot-ops-rsync) command. |
7676

7777
> [!TIP]
7878
> You must enable resource sync rules on the Azure IoT Operations instance to use the automatic asset discovery capabilities of the Akri services. To learn more, see [What is OPC UA asset discovery (preview)?](../discover-manage-assets/overview-akri.md).

articles/iot-operations/discover-manage-assets/howto-autodetect-opc-ua-assets-use-akri.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -39,12 +39,16 @@ In this article, you learn how to automatically discover and configure OPC UA as
3939

4040
# [Azure CLI](#tab/cli)
4141

42+
Run `rysnc enable` to enable resource sync rules on your Azure IoT Operations instance. This command also sets the required permissions on the custom location:
43+
44+
```bash
45+
az iot ops rsync enable
46+
```
47+
48+
If the signed-in CLI user doesn't have permission to look up the object ID of the K8 Bridge service principal, you can provide it explicitly using the `--k8-bridge-sp-oid` parameter:
49+
4250
```bash
43-
CUSTOM_LOCATION_NAME=$(az iot ops list -g <YOUR RESOURCE GROUP> --query "[0].extendedLocation.name" -o tsv)
44-
45-
ASSIGNEE=$(az ad sp list --display-name "K8 Bridge" --query "[0].appId" -o tsv)
46-
47-
az role assignment create --role "Azure Kubernetes Service Arc Contributor Role" --assignee $ASSIGNEE --scope $CUSTOM_LOCATION_NAME
51+
az iot ops rsync enable --k8-bridge-sp-oid <k8 bridge service principal object ID>
4852
```
4953
5054
---

0 commit comments

Comments
 (0)