Skip to content

Commit 1890226

Browse files
committed
Tidy include
1 parent 7a009e0 commit 1890226

File tree

4 files changed

+8
-4
lines changed

4 files changed

+8
-4
lines changed

articles/iot-operations/get-started/quickstart-process-telemetry.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,8 @@ Before you send data to the cloud for storage and analysis, you might want to pr
5050

5151
## Add a secret to your cluster
5252

53+
To access the lakehouse from a Data Processor pipeline, you need to enable your cluster to access the service principal details you created earlier. You need to configure your Azure Key Vault with the service principal details so that the cluster can retrieve them.
54+
5355
[!INCLUDE [add-cluster-secret](../includes/add-cluster-secret.md)]
5456

5557
## Create a basic pipeline

articles/iot-operations/includes/add-cluster-secret.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,10 @@ title: include file
33
description: include file
44
author: dominicbetts
55
ms.topic: include
6-
ms.date: 12/18/2023
6+
ms.date: 02/29/2024
77
ms.author: dobett
88
---
99

10-
To access the lakehouse from a Data Processor pipeline, you need to enable your cluster to access the service principal details you created earlier. You need to configure your Azure Key Vault with the service principal details so that the cluster can retrieve them.
11-
1210
Use the following command to add a secret to your Azure Key Vault that contains the client secret you made a note of when you created the service principal. You created the Azure Key Vault in the [Deploy Azure IoT Operations to an Arc-enabled Kubernetes cluster](../get-started/quickstart-deploy.md) quickstart:
1311

1412
```azurecli
@@ -59,7 +57,7 @@ To add the secret reference to your Kubernetes cluster, edit the **aio-default-s
5957

6058
1. Save the changes and exit from the editor.
6159

62-
The CSI driver updates secrets by using a polling interval, therefore the new secret isn't available to the pod until the polling interval is reached. To update the pod immediately, restart the pods for the component. To restart Data Processor, run the following commands:
60+
The CSI driver updates secrets by using a polling interval, therefore the new secret isn't available to the pod until the next polling interval. To update a component immediately, restart the pods for the component. For example, to restart the Data Processor component, run the following commands:
6361

6462
```console
6563
kubectl delete pod aio-dp-reader-worker-0 -n azure-iot-operations

articles/iot-operations/view-analyze-data/tutorial-anomaly-detection.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -79,6 +79,8 @@ To add a table to the `bakery_ops` database to store the anomaly data, navigate
7979

8080
### Add a secret to your cluster
8181

82+
To access the Azure Data Explorer database from a Data Processor pipeline, you need to enable your cluster to access the service principal details you created earlier. You need to configure your Azure Key Vault with the service principal details so that the cluster can retrieve them.
83+
8284
[!INCLUDE [add-cluster-secret](../includes/add-cluster-secret.md)]
8385

8486
## Assets and measurements

articles/iot-operations/view-analyze-data/tutorial-overall-equipment-effectiveness.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,8 @@ Make a note of your workspace ID and lakehouse ID, you need them later. You can
5858

5959
### Add a secret to your cluster
6060

61+
To access the lakehouse from a Data Processor pipeline, you need to enable your cluster to access the service principal details you created earlier. You need to configure your Azure Key Vault with the service principal details so that the cluster can retrieve them.
62+
6163
[!INCLUDE [add-cluster-secret](../includes/add-cluster-secret.md)]
6264

6365
## Understand the scenario and data

0 commit comments

Comments
 (0)