Skip to content

Commit 95af2ef

Browse files
authored
Merge pull request #202057 from w-azure/winona-blob
Added alert about container name restrictions
2 parents d73b744 + 660a3dc commit 95af2ef

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/iot-edge/how-to-deploy-blob.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,6 +107,9 @@ A deployment manifest is a JSON document that describes which modules to deploy,
107107

108108
Configure each property with an appropriate value, as indicated by the placeholders. If you are using the IoT Edge simulator, set the values to the related environment variables for these properties as described by [deviceToCloudUploadProperties](how-to-store-data-blob.md#devicetoclouduploadproperties) and [deviceAutoDeleteProperties](how-to-store-data-blob.md#deviceautodeleteproperties).
109109

110+
> [!TIP]
111+
> The name for your `target` container has naming restrictions, for example using a `$` prefix is unsupported. To see all restrictions, view [Container Names](/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata#container-names).
112+
110113
```json
111114
{
112115
"deviceAutoDeleteProperties": {
@@ -120,7 +123,7 @@ A deployment manifest is a JSON document that describes which modules to deploy,
120123
"cloudStorageConnectionString": "DefaultEndpointsProtocol=https;AccountName=<your Azure Storage Account Name>;AccountKey=<your Azure Storage Account Key>; EndpointSuffix=<your end point suffix>",
121124
"storageContainersForUpload": {
122125
"<source container name1>": {
123-
"target": "<target container name1>"
126+
"target": "<your-target-container-name>"
124127
}
125128
},
126129
"deleteAfterUpload": <true,false>

0 commit comments

Comments
 (0)