Skip to content

Commit 6f64468

Browse files
committed
Windows tutorial env handling, and SQL Server device requirements
1 parent 6c12c9f commit 6f64468

File tree

4 files changed

+19
-16
lines changed

4 files changed

+19
-16
lines changed

articles/iot-edge/tutorial-c-module-windows.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -98,21 +98,22 @@ The deployment manifest shares the credentials for your container registry with
9898

9999
1. In the Visual Studio solution explorer, open the **deployment.template.json** file.
100100

101-
2. Find the **registryCredentials** property in the $edgeAgent desired properties.
102-
103-
3. Update the property with your credentials, following this format:
101+
2. Find the **registryCredentials** property in the $edgeAgent desired properties. It should have your registry address autofilled from the information you provided when creating the project, and then username and password fields should contain variable names. For example:
104102

105103
```json
106104
"registryCredentials": {
107105
"<registry name>": {
108-
"username": "<username>",
109-
"password": "<password>",
106+
"username": "$CONTAINER_REGISTRY_USERNAME_<registry name>",
107+
"password": "$CONTAINER_REGISTRY_PASSWORD_<registry name>",
110108
"address": "<registry name>.azurecr.io"
111109
}
112110
}
113-
```
114111

115-
4. Save the deployment.template.json file.
112+
3. Open the **.env** file in your module solution. (It's hidden by default in the Solution Explorer, so you might need to select the **Show All Files** button to display it.) The .env file should contain the same username and password variables that you saw in the deployment.template.json file.
113+
114+
4. Add the **Username** and **Password** values from your Azure container registry.
115+
116+
5. Save your changes to the .env file.
116117

117118
### Update the module with custom code
118119

articles/iot-edge/tutorial-csharp-module-windows.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -89,21 +89,22 @@ The deployment manifest shares the credentials for your container registry with
8989

9090
1. In the Visual Studio solution explorer, open the **deployment.template.json** file.
9191

92-
2. Find the **registryCredentials** property in the $edgeAgent desired properties.
93-
94-
3. Update the property with your credentials, following this format:
92+
2. Find the **registryCredentials** property in the $edgeAgent desired properties. It should have your registry address autofilled from the information you provided when creating the project, and then username and password fields should contain variable names. For example:
9593

9694
```json
9795
"registryCredentials": {
9896
"<registry name>": {
99-
"username": "<username>",
100-
"password": "<password>",
97+
"username": "$CONTAINER_REGISTRY_USERNAME_<registry name>",
98+
"password": "$CONTAINER_REGISTRY_PASSWORD_<registry name>",
10199
"address": "<registry name>.azurecr.io"
102100
}
103101
}
104-
```
105102

106-
4. Save the deployment.template.json file.
103+
3. Open the **.env** file in your module solution. (It's hidden by default in the Solution Explorer, so you might need to select the **Show All Files** button to display it.) The .env file should contain the same username and password variables that you saw in the deployment.template.json file.
104+
105+
4. Add the **Username** and **Password** values from your Azure container registry.
106+
107+
5. Save your changes to the .env file.
107108

108109
### Update the module with custom code
109110

articles/iot-edge/tutorial-develop-for-windows.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ The IoT Edge runtime needs your registry credentials to pull your container imag
153153

154154
1. Open the **deployment.template.json** file in your module solution.
155155

156-
1. Find the **registryCredentials** property in the $edgeAgent desired properties and ensure it contains the correct information.
156+
1. Find the **registryCredentials** property in the $edgeAgent desired properties. It should have your registry address autofilled from the information you provided when creating the project, and then username and password fields should contain variable names. For example:
157157

158158
```json
159159
"registryCredentials": {

articles/iot-edge/tutorial-store-data-sql-server.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,8 @@ In this tutorial, you learn how to:
3535
Before beginning this tutorial, you should have gone through the previous tutorial to set up your development environment for Linux container development: [Develop IoT Edge modules for Linux devices](tutorial-develop-for-linux.md). By completing that tutorial, you should have the following prerequisites in place:
3636

3737
* A free or standard-tier [IoT Hub](../iot-hub/iot-hub-create-through-portal.md) in Azure.
38-
* A [Linux device running Azure IoT Edge](quickstart-linux.md)
38+
* An AMD64 [Linux device running Azure IoT Edge](quickstart-linux.md).
39+
* ARM devices, like Raspberry Pis, cannot run SQL Server. If you want to use SQL on an ARM device, you can sign up to try [Azure SQL Database Edge](https://azure.microsoft.com/services/sql-database-edge/) in preview.
3940
* A container registry, like [Azure Container Registry](https://docs.microsoft.com/azure/container-registry/).
4041
* [Visual Studio Code](https://code.visualstudio.com/) configured with the [Azure IoT Tools](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-tools).
4142
* [Docker CE](https://docs.docker.com/install/) configured to run Linux containers.

0 commit comments

Comments
 (0)