iotedgedev 3.3.4__zip → 3.3.5__zip

s/docs/{Migration-Guides.md → migration-guides.md}

@@ -1,9 +1,9 @@
 IoT Edge Dev Tool 0.82.0 provides support for the GA release of Azure IoT Edge and other new features, while on the other hand, introduces some breaking changes to better serve these new features. If you have used IoT Edge Dev Tool during the Azure IoT Edge public preview, this document will help you migrate your code and workflow to IoT Edge Dev Tool 0.82.0.
 
-### Retirement of `iotedgectl`
+## Retirement of `iotedgectl`
 With the GA release of Azure IoT Edge, iotedgectl (a.k.a, [azure-iot-edge-runtime-ctl](https://pypi.org/project/azure-iot-edge-runtime-ctl/)) is retired. In IoT Edge Dev Tool 0.82.0, we replace `iotedgectl` with the IoT Edge Simulator provided by the [iotedgehubdev CLI](https://pypi.org/project/iotedgehubdev/). The `setup`, `start`, and `stop` commands will now control IoT Edge Simulator instead.
 
-### Updated command list and options
+## Updated command list and options
 IoT Edge Dev Tool 0.82.0 comes with a new CLI UX. All commands are organized into four categories: `docker`, `iothub`, `simulator`, and `solution`. The general style is **iotedgedev _category_ _command_ --_parameter_**. For some frequently used commands, there is also an **iotedgedev _command_ --_parameter_** style shortcut (only if the shortcut won't cause confusion, similar to the relationship between `docker logs` and `docker container logs`). The shortcuts also add backward compatibility with some public preview style commands.
 
 Here is what you would see when you type `iotedgedev --help` (shortcuts are intentionally listed before the categories):
@@ -79,30 +79,30 @@ Options:
 
 Below is a full table of the public preview commands, new commands, and shortcuts (if applicable):
 
-Public Preview Command | New Command | Shortcut
--- | -- | --
-`--set-config` | `solution genconfig` | `genconfig `
-`solution --create --module --template` | `solution new --module/-t --template/-t` | `new`
-`init` | `solution init` | `init`
-`e2e` | `solution e2e` |
-`addmodule --template` | `solution add --template/-t` | `add --template/-t`
-`build --push --deploy` | `solution build --push/-p --deploy/-d` | `build --push/-p --deploy/-d`
-`push --deploy --no-build` | `solution push --deploy/-d --no-build` | `push --deploy/-d --no-build`
-`deploy` | `solution deploy` | `deploy`
-`monitor --timeout` | `iothub monitor --timeout/-t` | `monitor --timeout/-t`
-`azure --setup --credentials --service-principal --subscription --resource-group-location --resource-group-name --iothub-sku --iothub-name --edge-device-id --update-dotenv` | `iothub setup --credentials --service-principal --subscription --resource-group-location --resource-group-name --iothub-sku --iothub-name --edge-device-id --update-dotenv/-u` |  
-`modules --add --template` | `solution add --template` | `add --template/-t`
-`modules --build --push --deploy` | `solution build --push/-p --deploy/-d` | `build --push/-p --deploy/-d`
-`modules --push --deploy` | `solution push --deploy/-d --no-build` | `push --deploy/-d --no-build`
-`modules --deploy` | `solution deploy` | `deploy`
-`runtime --setup` | *deprecated, see [Retirement of `iotedgectl`](#retirement-of-iotedgectl) section* |  
-`runtime --start` | *deprecated, see [Retirement of `iotedgectl`](#retirement-of-iotedgectl) section* |  
-`runtime --stop` | *deprecated, see [Retirement of `iotedgectl`](#retirement-of-iotedgectl) section* |  
-`runtime --restart` | *deprecated, see [Retirement of `iotedgectl`](#retirement-of-iotedgectl) section* |  
-`runtime --status` | *deprecated, see [Retirement of `iotedgectl`](#retirement-of-iotedgectl) section* |  
-`docker --setup-registry` | `docker setup` |  
-`docker --clean --remove-modules --remove-containers --remove-images` | `docker clean --modules/-m --containers/-c --image/-i` |  
-`docker --logs --show-logs --save-logs` | `docker log --show/-l --save/-s` | `docker log --show/-l --save/-s`
+| Public Preview Command                                                                                                                                                       | New Command                                                                                                                                                                    | Shortcut                         |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------- |
+| `--set-config`                                                                                                                                                               | `solution genconfig`                                                                                                                                                           | `genconfig `                     |
+| `solution --create --module --template`                                                                                                                                      | `solution new --module/-t --template/-t`                                                                                                                                       | `new`                            |
+| `init`                                                                                                                                                                       | `solution init`                                                                                                                                                                | `init`                           |
+| `e2e`                                                                                                                                                                        | `solution e2e`                                                                                                                                                                 |
+| `addmodule --template`                                                                                                                                                       | `solution add --template/-t`                                                                                                                                                   | `add --template/-t`              |
+| `build --push --deploy`                                                                                                                                                      | `solution build --push/-p --deploy/-d`                                                                                                                                         | `build --push/-p --deploy/-d`    |
+| `push --deploy --no-build`                                                                                                                                                   | `solution push --deploy/-d --no-build`                                                                                                                                         | `push --deploy/-d --no-build`    |
+| `deploy`                                                                                                                                                                     | `solution deploy`                                                                                                                                                              | `deploy`                         |
+| `monitor --timeout`                                                                                                                                                          | `iothub monitor --timeout/-t`                                                                                                                                                  | `monitor --timeout/-t`           |
+| `azure --setup --credentials --service-principal --subscription --resource-group-location --resource-group-name --iothub-sku --iothub-name --edge-device-id --update-dotenv` | `iothub setup --credentials --service-principal --subscription --resource-group-location --resource-group-name --iothub-sku --iothub-name --edge-device-id --update-dotenv/-u` |
+| `modules --add --template`                                                                                                                                                   | `solution add --template`                                                                                                                                                      | `add --template/-t`              |
+| `modules --build --push --deploy`                                                                                                                                            | `solution build --push/-p --deploy/-d`                                                                                                                                         | `build --push/-p --deploy/-d`    |
+| `modules --push --deploy`                                                                                                                                                    | `solution push --deploy/-d --no-build`                                                                                                                                         | `push --deploy/-d --no-build`    |
+| `modules --deploy`                                                                                                                                                           | `solution deploy`                                                                                                                                                              | `deploy`                         |
+| `runtime --setup`                                                                                                                                                            | *deprecated, see [Retirement of `iotedgectl`](#retirement-of-iotedgectl) section*                                                                                              |
+| `runtime --start`                                                                                                                                                            | *deprecated, see [Retirement of `iotedgectl`](#retirement-of-iotedgectl) section*                                                                                              |
+| `runtime --stop`                                                                                                                                                             | *deprecated, see [Retirement of `iotedgectl`](#retirement-of-iotedgectl) section*                                                                                              |
+| `runtime --restart`                                                                                                                                                          | *deprecated, see [Retirement of `iotedgectl`](#retirement-of-iotedgectl) section*                                                                                              |
+| `runtime --status`                                                                                                                                                           | *deprecated, see [Retirement of `iotedgectl`](#retirement-of-iotedgectl) section*                                                                                              |
+| `docker --setup-registry`                                                                                                                                                    | `docker setup`                                                                                                                                                                 |
+| `docker --clean --remove-modules --remove-containers --remove-images`                                                                                                        | `docker clean --modules/-m --containers/-c --image/-i`                                                                                                                         |
+| `docker --logs --show-logs --save-logs`                                                                                                                                      | `docker log --show/-l --save/-s`                                                                                                                                               | `docker log --show/-l --save/-s` |
 
 ### Deployment manifest template
 IoT Edge Dev Tool 0.82.0 relies on the deployment manifest template to build the solution (see [Deprecation of `ACTIVE_MODULES`](#deprecation-of-active_modules) section for details). By default, it's the `deployment.template.json` file in the root of the solution folder, but you can also customize it with the `DEPLOYMENT_CONFIG_TEMPLATE_FILE` environment variable. The major difference between deployment manifest template and deployment manifest is that module image URLs in deployment manifest template can be placeholders (whose format looks like `${MODULES.filtermodule.amd64}`). The image placeholders can help you easily update the referenced module and image platform without typing lengthy image URLs. When building solutions, IoT Edge Dev Tool will parse the image placeholders, expand them with the actual image URLs and save the results in the deployment manifest in the config output folder. By default, it's the `deployment.json` file in the `config` folder, but you can also customize it with the `DEPLOYMENT_CONFIG_FILE` and `CONFIG_OUTPUT_DIR` environment variables. In addition, when adding modules, IoT Edge Dev Tool will add a corresponding section for the module in the deployment manifest template with `${MODULES.<module-name>.amd64}` as the image.

s/docs/quickstart.md

@@ -0,0 +1,152 @@
+# Quickstart
+
+This quickstart will run a container, create a solution, setup Azure resources, build and deploy modules to your device, setup and start the IoT Edge simulator, monitor messages flowing into IoT Hub, and finally deploy to the IoT Edge runtime.
+
+At the end of this quickstart, you should have the following:
+
+- Development environment.
+- IoT Hub deployed in your Azure subscription.
+- A directory with the [IoT edge deployment manifest](https://docs.microsoft.com/en-us/azure/iot-edge/module-composition?view=iotedge-2020-11), [.env file](.env.tmp) with the environment variables needed for the `iotedgedev` tool, and the source file of a custom IoT edge module (`filtermodule`).
+- The docker image of the `filtermodule`.
+- Deploying the IoT edge modules defined in the manifest on a VM or IoT Edge simulator.
+- Monitoring the messages sent to the IoT Hub.
+- Cleaning up the docker containers and images.
+
+## Pre-requisites
+
+- Docker (see [Install Docker docs](environment-setup/install-docker) for details) and add user to `docker` Unix group (see [documentation](https://docs.docker.com/engine/install/linux-postinstall/)).
+
+## Quickstart steps
+
+1. Setup your environment
+
+    There are three options to setup your environment:
+
+    - Setup the development environment manually. Please follow the [Manual Development Machine Setup Wiki](environment-setup/manual-dev-machine-setup).
+    - Starting the devcontainer in VS Code (see [Developing inside a Container](https://code.visualstudio.com/docs/remote/containers) for steps on how to do so).
+    - Starting the devcontainer with Docker. Please follow the [Run the IoT Edge Dev Container with Docker docs](environment-setup/run-devcontainer-docker).
+
+1. Initialize IoT Edge solution and setup Azure resources.
+
+    ```sh
+    iotedgedev init <foldername>
+    ```
+
+    > `iotedgedev init` will create a solution in a new folder and setup your Azure IoT Hub in a single command. The solution comes with a default C# module named `filtermodule`.
+
+    <details>
+    <summary>More information</summary>
+
+    1. You will see structure of current folder like below:
+
+    ```tree
+        │  .env
+        │  .gitignore
+        │  deployment.debug.template.json
+        │  deployment.template.json
+        │
+        ├─.vscode
+        │      launch.json
+        │
+        └─modules
+            └─filtermodule
+                │  .gitignore
+                │  Dockerfile.amd64
+                │  Dockerfile.amd64.debug
+                │  Dockerfile.arm32v7
+                │  Dockerfile.windows-amd64
+                │  filtermodule.csproj
+                │  module.json
+                │  Program.cs
+    ```
+
+    1. Open `.env` file, you will see the `IOTHUB_CONNECTION_STRING` and `DEVICE_CONNECTION_STRING` environment variables filled correctly.
+    2. Open `deployment.template.json` file.
+        1. You will see below section in the modules section:
+
+        ```json
+        "filtermodule": {
+            "version": "1.0",
+            "type": "docker",
+            "status": "running",
+            "restartPolicy": "always",
+            "settings": {
+                "image": "${MODULES.filtermodule}",
+                "createOptions": {}
+            }
+        }
+        ```
+
+        1. Two default routes are added:
+
+        ```json
+        "routes": {
+            "sensorTofiltermodule": "FROM /messages/modules/tempSensor/outputs/temperatureOutput INTO BrokeredEndpoint(\"/modules/filtermodule/inputs/input1\")",
+            "filtermoduleToIoTHub": "FROM /messages/modules/filtermodule/outputs/* INTO $upstream"
+        }
+        ```
+
+    3. You will see privacy statement like below:
+
+        ```txt
+        Welcome to iotedgedev!
+        -------------------------
+        Telemetry
+        ---------
+        The iotedgedev collects usage data in order to improve your experience.
+        The data is anonymous and does not include commandline argument values.
+        The data is collected by Microsoft.
+        
+        You can change your telemetry settings by updating 'collect_telemetry' to 'no' in ~/.iotedgedev/setting.ini
+        ```
+
+    </details>
+
+3. Build IoT Edge module images.
+
+    ```sh
+    iotedgedev build
+    ```
+
+    > This step will build user modules in deployment.template.json targeting amd64 platform.
+
+    <details>
+    <summary>More information</summary>
+
+    1. You will see a "BUILD COMPLETE" for each module and no error messages in the terminal output.
+    2. Open `config/deployment.amd64.json` file, you will see the module image placeholders expanded correctly.
+    3. Run `sudo docker image ls`, you will see the module images you just built.
+
+    </details>
+
+4. Run IoT Edge modules.
+
+    Edge modules can be started in two different ways using `iotedgedev`:
+
+    - Deploying them on a VM; please find the steps to do so in [Set up and start modules on a virtual machine](run-modules-on-vm);
+    - or in your own development machine using the `iotedgedev` simulator; please follow [Set up and start the IoT Edge Simulator](run-modules-on-simulator).
+
+5. Monitor messages sent from device to IoT Hub.
+
+    ```sh
+    iotedgedev monitor
+    ```
+
+    <details>
+    <summary>More information</summary>
+
+    1. You will see your expected messages sending to IoT Hub
+    2. Stopping the monitor doesn't stop the simulator. It will continue running until it is explicitely stopped using `iotedgedev stop` and at that time all containers used by the simulator will be cleaned up.
+
+    </details>
+
+6. Stop docker containers and remove images.
+
+    ```sh
+    # stop containers started by the simulator
+    iotedgedev stop
+    # remove stopped containers
+    iotedgedev docker clean -c
+    # remove docker images
+    iotedgedev docker clean -
+    ```

s/docs/run-modules-on-simulator.md

@@ -0,0 +1,18 @@
+
+# Set up and start the IoT Edge Simulator
+
+In order to run the modules defined in a deployment configuration (such as `config/deployment.amd64.json`) on your development machine using the `iotedgedev` simulator run the following command:
+
+```sh
+iotedgedev start --setup --file config/deployment.amd64.json
+```
+
+> The [IoT Edge Hub Simulator](https://github.com/Azure/iotedgehubdev) starts the containers defined in the IoT edge device manifest in your local machine.
+
+<details>
+<summary>More information</summary>
+
+1. You will see an "IoT Edge Simulator has been started in solution mode." message at the end of the terminal output
+2. Run ` docker ps`, you will see your modules running as well as an edgeHubDev container
+
+</details>

s/docs/run-modules-on-vm.md

@@ -0,0 +1,54 @@
+# Set up and start modules on a virtual machine
+
+1. [**Set up virtual machine to run Azure IoT Edge**](https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-ubuntuvm)
+2. **Create and configure an ACR (Azure Container Registry)**
+   1. [Create an Azure Container Registry](https://docs.microsoft.com/en-us/azure/container-registry/container-registry-get-started-portal)
+   2. Configure `.env` that was generated in the `iotedgedev init` step with the ACR by modifying these lines with appropriate values:
+
+       ```sh
+       CONTAINER_REGISTRY_SERVER="localhost:5000"
+       CONTAINER_REGISTRY_USERNAME=""
+       CONTAINER_REGISTRY_PASSWORD=""
+       ```
+
+3. **Push modules to ACR with**
+
+    `iotedgedev push`
+
+4. **Add registry credentials to deployment manifest**
+
+    1. Replace generated `deployment.template.json` field `registryCredentials` with
+
+        ```json
+        "registryCredentials": {
+              "privateAcr": {
+                "username": "$CONTAINER_REGISTRY_USERNAME",
+                "password": "$CONTAINER_REGISTRY_PASSWORD",
+                "address": "$CONTAINER_REGISTRY_SERVER"
+              }
+            }
+        ```
+
+        > Note: `privateAcr` can be renamed to anything else
+    2. Regenerate the `config/deployment.amd64.json`
+
+        `iotedgedev genconfig`
+
+5. **Deploy modules to device**
+
+    `iotedgedev solution deploy`
+
+6. **Troubleshooting**
+
+    - Verify modules deployment status via executing:
+
+        ```bash
+        # Populate variables from .env
+        edge_device_id=$(dotenv get DEVICE_CONNECTION_STRING |  grep -oP '(?<=DeviceId=).*(?=;Shared)')
+        iot_hub_connection_string=$(dotenv get IOTHUB_CONNECTION_STRING)
+        # Execute query
+        az iot hub module-identity list --device-id $edge_device_id --login $iot_hub_connection_string
+        ```
+
+    - [Troubleshoot IoT Edge devices from the Azure portal](https://docs.microsoft.com/en-us/azure/iot-edge/troubleshoot-in-portal)
+    - SSH into the virtual machine and follow [troubleshoot your IoT Edge device](https://docs.microsoft.com/en-us/azure/iot-edge/troubleshoot)

s/docs/{Troubleshooting.md → troubleshooting.md}

@@ -1,20 +1,21 @@
 1. `Invalid Reference Format`
-    ```
+
+    ```sh
     500 Server Error: Internal Server Error for url: http+docker://localunixsocket/v1.30/images
     500 Server Error: Internal Server Error ("invalid reference format")
     ```
 
     Solution: You likely installed Docker via `sudo apt install docker.io`. Use the proper steps for [CE here](https://docs.docker.com/engine/installation/linux/docker-ce/ubuntu/#install-docker-ce), or use the [convenience script](https://docs.docker.com/engine/installation/linux/docker-ce/ubuntu/#install-using-the-convenience-script).
 
-1. `('Connection aborted.', error(2, 'No such file or directory'))`
+2. `('Connection aborted.', error(2, 'No such file or directory'))`
 
     This means that you have likely do not have `DOCKER_HOST` Environment Variable set.
 
-    ```
+    ```sh
     ERROR: Could not login to Container Registry. Please verify your credentials in CONTAINER_REGISTRY_ environment variables.
     ```
 
-    ```
+    ```sh
     ('Connection aborted.', error(2, 'No such file or directory'))
     ERROR: Could not connect to docker daemon.
     ERROR: Docker is unavailable

s/docs/{Usage.md → usage.md}

@@ -1,26 +1,26 @@
 # Usage
 
-You can use the IoT Edge Dev Tool container to avoid having to install all the dependencies on your local dev machine. The only thing you need to install is Docker. All of the other dev dependencies are included in the container. Please see the [Quickstart](quickstart-with-IoT-Edge-Dev-Container) to learn more.
+You can use the IoT Edge Dev Tool container to avoid having to install all the dependencies on your local dev machine. The only thing you need to install is Docker. All of the other dev dependencies are included in the container. Please see the [Quickstart](quickstart) to learn more.
 
-To set up development machines manually instead of using the IoT Edge Dev Container, please see the [Manual Development Machine Setup Wiki](manual-Dev-Machine-Setup).
+To set up development machines manually instead of using the IoT Edge Dev Container, please see the [Manual Development Machine Setup Wiki](environment-setup/manual-dev-machine-setup).
 
 If you are using a separate Edge device, like a Raspberry Pi, you do not need to run all of these steps on your IoT Edge device, you can install and setup Edge runtime directly on the device. See the [Edge Device Setup](edge-device-setup) wiki page for more information on setting up your Edge device.
 
-Note: See the ["Test Coverage"](test-coverage) wiki page to see what the IoT Edge Dev Tool has been tested with.
+**Note:** See the ["Test Coverage"](test-coverage) wiki page to see what the IoT Edge Dev Tool has been tested with.
 
 1. **Initialize IoT Edge solution and setup Azure resources**
 
     ```sh
-    iotedgedev init
+    iotedgedev init <folder_name>
     ```
 
-    `iotedgedev init` will run both `iotedgedev new .` and `iotedgedev iothub setup`, which will create a new solution and setup your Azure resources in a single command.
+    `iotedgedev init` will run both `iotedgedev new <folder_name>` and `iotedgedev iothub setup`, which will create a new solution and setup your Azure resources in a single command. If `<folder_name>` is not specified, it will default to `.`.
 
     If you want to use your existing IoT Hub and IoT Edge device, you can run `iotedgedev new .`, and update the `.env` file with the IoT Hub connection string and IoT Edge device connection string.
 
     `iotedgedev init` and `iotedgedev new .` will add a default C# module named `filtermodule` to the solution. To customize this behavior, append the parameters `--module <module-name--template <template>`.
 
-1. **Add modules to IoT Edge solution**
+2. **Add modules to IoT Edge solution**
 
     ```sh
     iotedgedev add <module-name--template <template>
@@ -28,7 +28,7 @@ Note: See the ["Test Coverage"](test-coverage) wiki page to see what the IoT Edg
 
     Currently the available template values are `c`, `csharp`, `java`, `nodejs`, `python`, `csharpfunction`. We are working on supporting more templates.
 
-1. **Build IoT Edge module images**
+3. **Build IoT Edge module images**
 
     ```sh
     sudo iotedgedev build
@@ -38,7 +38,7 @@ Note: See the ["Test Coverage"](test-coverage) wiki page to see what the IoT Edg
     * You are on Windows or macOS.
     * You are on Linux, and you have followed the [post-installation steps for Linux](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user) to allow running Docker commands without `sudo`.
 
-1. **Setup the [IoT Edge Simulator]((https://pypi.org/project/iotedgehubdev/).)**
+4. **Setup the [IoT Edge Simulator](https://pypi.org/project/iotedgehubdev/)**
 
     ```sh
     sudo iotedgedev setup
@@ -48,7 +48,7 @@ Note: See the ["Test Coverage"](test-coverage) wiki page to see what the IoT Edg
 
     You can avoid `sudo` if you are on Windows, and running IoT Edge Dev Tool outside Docker container.
 
-1. **Start the IoT Edge Simulator to run the solution**
+5. **Start the IoT Edge Simulator to run the solution**
 
     ```sh
     sudo iotedgedev start
@@ -60,13 +60,13 @@ Note: See the ["Test Coverage"](test-coverage) wiki page to see what the IoT Edg
     * You are on Windows or macOS.
     * You are on Linux, and you have followed the [post-installation steps for Linux](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user) to allow running Docker commands without `sudo`.
 
-1. **Monitor messages sent from IoT Edge Simulator to IoT Hub**
+6. **Monitor messages sent from IoT Edge Simulator to IoT Hub**
 
     ```sh
     iotedgedev monitor
     ```
 
-1. **Stop the IoT Edge Simulator**
+7. **Stop the IoT Edge Simulator**
 
     ```sh
     sudo iotedgedev stop
@@ -76,12 +76,12 @@ Note: See the ["Test Coverage"](test-coverage) wiki page to see what the IoT Edg
     * You are on Windows or macOS.
     * You are on Linux, and you have followed the [post-installation steps for Linux](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user) to allow running Docker commands without `sudo`.
 
-1. **Setup the IoT Edge Runtime**
+8. **Setup the IoT Edge Runtime**
 
     1. Copy the device connection string from the `DEVICE_CONNECTION_STRING` environment variable in the `.env` file, [Azure Portal](https://docs.microsoft.com/en-us/azure/iot-edge/how-to-register-device-portal#retrieve-the-connection-string), or [Azure CLI](https://docs.microsoft.com/en-us/azure/iot-edge/how-to-register-device-cli#retrieve-the-connection-string).
-    1. Follow [Edge Device Setup](edge-device-setup) to setup and start the IoT Edge Runtime with the copied device connection string
+    2. Follow [Edge Device Setup](edge-device-setup) to setup and start the IoT Edge Runtime with the copied device connection string
 
-1. **Push IoT Edge module images**
+9. **Push IoT Edge module images**
 
     ```sh
     sudo iotedgedev push
@@ -91,7 +91,7 @@ Note: See the ["Test Coverage"](test-coverage) wiki page to see what the IoT Edg
     * You are on Windows or macOS.
     * You are on Linux, and you have followed the [post-installation steps for Linux](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user) to allow running Docker commands without `sudo`.
 
-1. **Deploy modules to IoT Edge device**
+10. **Deploy modules to IoT Edge device**
 
     ```sh
     iotedgedev deploy
@@ -99,24 +99,23 @@ Note: See the ["Test Coverage"](test-coverage) wiki page to see what the IoT Edg
 
     You can also combine push and deploy with `iotedgedev push --deploy`
 
-1. **Deploy modules with automatic deployments to IoT Hub**
+11. **Deploy modules with automatic deployments to IoT Hub**
 
     ```sh
     iotedgedev iothub deploy --name TEXT --priority TEXT --target-condition TEXT
     ```
-    
+
     You can also combine tagging the device and deploy with the `--device-tag TEXT` flag
 
     > More information on how automatic deployments work can be found here: <https://docs.microsoft.com/en-us/azure/iot-edge/module-deployment-monitoring?view=iotedge-2020-11>
 
-1. **Tag IoT Edge Device**
+12. **Tag IoT Edge Device**
 
     ```sh
     iotedgedev solution tag --tags TEXT
     ```
 
-
-1. **Monitor messages sent from IoT Edge Runtime to IoT Hub**
+13. **Monitor messages sent from IoT Edge Runtime to IoT Hub**
 
     ```sh
     iotedgedev monitor

s/iotedgedev/__init__.py

@@ -2,5 +2,5 @@
 
 __author__ = 'Microsoft Corporation'
 __email__ = 'opencode@microsoft.com'
-__version__ = '3.3.4'
+__version__ = '3.3.5'
 __AIkey__ = 'fed7fc65-5b4a-4e66-9d46-c5f016d4e2b4'

s/iotedgedev/azurecli.py

@@ -148,10 +148,13 @@ class AzureCli:
                         pass
                 else:
                     err = None
+                    err_list = []
                     try:
-                        err = stderr_queue.get_nowait()
+                        while True:
+                            err_list.append(stderr_queue.get_nowait())
                     except Empty:
                         pass
+                    err = "\n".join(err_list)
                     # Avoid empty sys.excepthook errors from underlying future
                     # There is already a uAMQP issue in work for this
                     # https://github.com/Azure/azure-uamqp-python/issues/30
@@ -465,9 +468,16 @@ class AzureCli:
                 self.output.prompt(
                     "Creating IoT Hub. Please wait as this could take a few minutes to complete...")
 
-                result = self.invoke_az_cli_outproc(["iot", "hub", "create", "--name", value, "--resource-group",
-                                                     resource_group, "--sku", sku, "--query", "[].{\"IoT Hub\":name}", "--out", "table"],
-                                                    f("Could not create the IoT Hub {value} in {resource_group} with sku {sku}."), stdout_io=io, stderr_io=error_io)
+                cmd = ["iot", "hub", "create", "--name", value, "--resource-group", resource_group, "--sku", sku, "--query", "[].{\"IoT Hub\":name}", "--out", "table"]
+                if sku == "F1":
+                    cmd = cmd + ["--partition-count", "2"]
+                    # the default partition-count is 4, but F1 allows only 2
+                    # from `az iot hub create --help`:
+                    #   The partition count is the number of partitions that the IoT Hub uses to distribute messages.
+                    #   The default value is 4.
+                    # In Azure Portal the default and only value is 2.
+
+                result = self.invoke_az_cli_outproc(cmd, f("Could not create the IoT Hub {value} in {resource_group} with sku {sku}."), stdout_io=io, stderr_io=error_io)
                 if not result and error_io.getvalue():
                     self.output.error(error_io.getvalue())
                     self.output.line()