Merge pull request #164466 from kgremban/jul2-77690-createoptions

Fix createOptions empty strings

Author: v-andreaco

articles/iot-edge/how-to-configure-proxy-support.md

@@ -352,7 +352,7 @@ With the environment variables included, your module definition should look like
     "type": "docker",
     "settings": {
         "image": "mcr.microsoft.com/azureiotedge-hub:1.1",
-        "createOptions": ""
+        "createOptions": "{}"
     },
     "env": {
         "https_proxy": {

articles/iot-edge/how-to-connect-downstream-iot-edge-device.md

@@ -382,7 +382,7 @@ The API proxy module was designed to be customized to handle most common gateway
                        "edgeAgent": {
                            "settings": {
                                "image": "mcr.microsoft.com/azureiotedge-agent:1.2",
-                               "createOptions": ""
+                               "createOptions": "{}"
                            },
                            "type": "docker"
                        },

articles/iot-edge/how-to-deploy-cli-at-scale.md

@@ -129,7 +129,7 @@ Here's a basic layered deployment manifest with one module as an example:
         "properties.desired.modules.SimulatedTemperatureSensor": {
           "settings": {
             "image": "mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.0",
-              "createOptions": ""
+              "createOptions": "{}"
           },
           "type": "docker",
           "status": "running",

articles/iot-edge/module-composition.md

@@ -325,7 +325,7 @@ The following example shows what a valid deployment manifest document may look l
             "type": "docker",
             "settings": {
               "image": "mcr.microsoft.com/azureiotedge-agent:1.1",
-              "createOptions": ""
+              "createOptions": "{}"
             }
           },
           "edgeHub": {