Skip to content

Commit 6b421dc

Browse files
committed
Add moniker range
1 parent fd5bf0e commit 6b421dc

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

articles/iot-edge/how-to-access-host-storage-from-module.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ services: iot-edge
1414

1515
[!INCLUDE [iot-edge-version-all-supported](includes/iot-edge-version-all-supported.md)]
1616

17+
::: moniker range=">=iotedge-1.4"
18+
1719
IoT Edge modules can use storage on the host IoT Edge device itself for improved reliability, especially when operating offline.
1820

1921
## Configure system modules to use persistent storage
@@ -109,9 +111,14 @@ There are several ways to manage directory permissions on Linux systems, includi
109111
sudo chown 1000 <HostStoragePath>
110112
sudo chmod 700 <HostStoragePath>
111113
```
114+
::: moniker-end
115+
116+
::: moniker range="<=iotedge-2020-11"
112117

113118
When modules invoke the IoT Edge daemon's workload API to encrypt data, the encryption key is derived using the module ID and module's generation ID. A generation ID is used to protect secrets if a module is removed from the deployment and then another module with the same module ID is later deployed to the same device. You can view a module's generation ID using the Azure CLI command [az iot hub module-identity show](/cli/azure/iot/hub/module-identity).
114119

120+
::: moniker-end
121+
115122
If you want to share files between modules across generations, they must not contain any secrets or they will fail to be decrypted.
116123

117124
## Next steps

0 commit comments

Comments
 (0)