iotedgedev 3.3.4__zip

s/docs/Command-List.md

@@ -0,0 +1,564 @@
+# Commands
+
+## iotedgedev
+
+```text
+Usage: iotedgedev [OPTIONS] COMMAND [ARGS]...
+
+Options:
+  --version   Show the version and exit.
+  -h, --help  Show this message and exit.
+
+Commands:
+  add        Add a new module to the solution
+  build      Build the solution
+  deploy     Deploy solution to IoT Edge device
+  genconfig  Expand environment variables and placeholders in deployment manifest template file and copy to config folder
+  init       Create a new IoT Edge solution and provision Azure resources
+  log        Open a new terminal window for EdgeAgent, EdgeHub and each Edge module and save to LOGS_PATH
+  monitor    Monitor messages from IoT Edge device to IoT Hub
+  new        Create a new IoT Edge solution
+  push       Push module images to container registry
+  setup      Setup IoT Edge simulator. This must be done before starting
+  start      Start IoT Edge simulator
+  stop       Stop IoT Edge simulator
+  docker     Manage Docker
+  iothub     Manage IoT Hub and IoT Edge devices
+  simulator  Manage IoT Edge simulator
+  solution   Manage IoT Edge solutions
+```
+
+## iotedgedev add
+
+```text
+Usage: iotedgedev add [OPTIONS] NAME
+
+  Add a new module to the solution, where NAME is the module name
+
+Options:
+  -t, --template [c|csharp|java|nodejs|python|csharpfunction]
+                                  Specify the template used to create the default module  [default: csharp]
+  -g, --group-id TEXT             (Java modules only) Specify the groupId  [default: com.edgemodule]
+  -h, --help                      Show this message and exit.
+```
+
+## iotedgedev build
+
+```text
+Usage: iotedgedev build [OPTIONS]
+
+  Build the solution
+
+Options:
+  -p, --push           Push module images to container registry  [default: False]
+  -d, --deploy         Deploy modules to Edge device using deployment.json in the config folder  [default: False]
+  -f, --file TEXT      Specify the deployment manifest template file [default: deployment.template.json]
+  -P, --platform TEXT  Specify the platform  [default: amd64]
+  -h, --help           Show this message and exit.
+```
+
+## iotedgedev deploy
+
+```text
+Usage: iotedgedev deploy [OPTIONS]
+
+  Deploy solution to IoT Edge device
+
+Options:
+  -f, --file TEXT  Specify the deployment manifest file  [default: config\deployment.amd64.json]
+  -h, --help       Show this message and exit.
+```
+
+## iotedgedev genconfig
+
+```text
+Usage: iotedgedev genconfig [OPTIONS]
+
+  Expand environment variables and placeholders in deployment manifest
+  template file and copy to config folder
+
+Options:
+  -f, --file TEXT      Specify the deployment manifest template file  [default: deployment.template.json]
+  -P, --platform TEXT  Specify the platform  [default: amd64]
+  -h, --help           Show this message and exit.
+```
+
+## iotedgedev init
+
+```text
+Usage: iotedgedev init [OPTIONS]
+
+  Create a new IoT Edge solution and provision Azure resources
+
+Options:
+  -er, --edge-runtime-version TEXT
+                                  Specify the IoT Edge Runtime Version. Currently available 1.0 and 1.1  [default: 1.1]
+  -m, --module TEXT               Specify the name of the default module  [default: filtermodule]
+  -t, --template [c|csharp|java|nodejs|python|csharpfunction]
+                                  Specify the template used to create the default module  [default: csharp]
+  -g, --group-id TEXT             (Java modules only) Specify the groupId  [default: com.edgemodule]
+  -h, --help                      Show this message and exit.
+```
+
+## iotedgedev log
+
+```text
+Usage: iotedgedev log [OPTIONS]
+
+  Open a new terminal window for EdgeAgent, EdgeHub and each Edge module and
+  save to LOGS_PATH. You can configure the terminal command with LOGS_CMD.
+
+Options:
+  -l, --show  Open a new terminal window for EdgeAgent, EdgeHub and each Edge module. You can configure the terminal command with LOGS_CMD.  [default: False]
+  -s, --save  Save EdgeAgent, EdgeHub and each Edge module logs to LOGS_PATH.  [default: False]
+  -h, --help  Show this message and exit.
+```
+
+## iotedgedev monitor
+
+```text
+Usage: iotedgedev monitor [OPTIONS]
+
+  Monitor messages from IoT Edge device to IoT Hub
+
+Options:
+  -t, --timeout TEXT  Specify number of seconds to monitor for messages
+  -h, --help          Show this message and exit.
+```
+
+## iotedgedev new
+
+```text
+Usage: iotedgedev new [OPTIONS] NAME
+
+  Create a new IoT Edge solution, where NAME is the solution folder name.
+  Use "." as NAME to create in the current folder.
+
+Options:
+  -m, --module TEXT               Specify the name of the default module  [default: filtermodule]
+  -t, --template [c|csharp|java|nodejs|python|csharpfunction]
+                                  Specify the template used to create the default module  [default: csharp]
+  -g, --group-id TEXT             (Java modules only) Specify the groupId  [default: com.edgemodule]
+  -h, --help                      Show this message and exit.
+```
+
+## iotedgedev push
+
+```text
+Usage: iotedgedev push [OPTIONS]
+
+  Push module images to container registry
+
+Options:
+  -d, --deploy         Deploy modules to Edge device using deployment.json in the config folder  [default: False]
+  --no-build           Inform the push command to not build module images before pushing to container registry  [default: False]
+  -f, --file TEXT      Specify the deployment manifest template file  [default: deployment.template.json]
+  -P, --platform TEXT  Specify the platform  [default: amd64]
+  -h, --help           Show this message and exit.
+```
+
+## iotedgedev setup
+
+```text
+Usage: iotedgedev setup [OPTIONS]
+
+  Setup IoT Edge simulator. This must be done before starting
+
+Options:
+  -g, --gateway-host TEXT  GatewayHostName value for the module to connect.  [default: <your hostname>]
+  -h, --help               Show this message and exit.
+```
+
+## iotedgedev start
+
+```text
+Usage: iotedgedev start [OPTIONS]
+
+  Start IoT Edge simulator. To start in solution mode, use `iotedgdev
+  simulator start -s [-v] [-b]`. To start in single module mode, use
+  `iotedgedev simulator start -i input1,input2 [-p 53000]`
+
+Options:
+  -u, --setup          Setup IoT Edge simulator before starting.  [default: False]
+  -s, --solution       Start IoT Edge simulator in solution mode using the deployment.json in config folder.  [default: False]
+  -v, --verbose        Show the solution container logs.  [default: False]
+  -b, --build          Build the solution before starting IoT Edge simulator in solution mode.  [default: False]
+  -f, --file TEXT      Specify the deployment manifest file. When `--build` flag is set, specify a deployment manifest template and it will be built.  [default: config\deployment.amd64.json]
+  -P, --platform TEXT  Specify the platform  [default: amd64]
+  -i, --inputs TEXT    Start IoT Edge simulator in single module mode using the specified comma-separated inputs of the target module, e.g., `input1,input2`.
+  -p, --port INTEGER   Port of the service for sending message.  [default: 53000]
+  -h, --help           Show this message and exit.
+```
+
+## iotedgedev stop
+
+```text
+Usage: iotedgedev stop [OPTIONS]
+
+  Stop IoT Edge simulator
+
+Options:
+  -h, --help  Show this message and exit.
+```
+
+## iotedgedev docker
+
+```text
+Usage: iotedgedev docker [OPTIONS] COMMAND [ARGS]...
+
+  Manage Docker
+
+Options:
+  -h, --help  Show this message and exit.
+
+Commands:
+  clean  Remove all the containers and images
+  log    Open a new terminal window for EdgeAgent, EdgeHub and each Edge module and save to LOGS_PATH
+  setup  Pull Edge runtime images from MCR and push to your specified container registry
+```
+
+## iotedgedev docker clean
+
+```text
+Usage: iotedgedev docker clean [OPTIONS]
+
+  Remove all the containers and images
+
+Options:
+  -m, --module     Remove only the Edge module containers and images, not
+                   EdgeAgent or EdgeHub  [default: False]
+  -c, --container  Remove all the containers  [default: False]
+  -i, --image      Remove all the images  [default: False]
+  -h, --help       Show this message and exit.
+```
+
+## iotedgedev docker log
+
+```text
+Usage: iotedgedev docker log [OPTIONS]
+
+  Open a new terminal window for EdgeAgent, EdgeHub and each Edge module and
+  save to LOGS_PATH. You can configure the terminal command with LOGS_CMD.
+
+Options:
+  -l, --show  Open a new terminal window for EdgeAgent, EdgeHub and each Edge module. You can configure the terminal command with LOGS_CMD.  [default: False]
+  -s, --save  Save EdgeAgent, EdgeHub and each Edge module logs to LOGS_PATH.  [default: False]
+  -h, --help  Show this message and exit.
+```
+
+## iotedgedev docker setup
+
+```text
+Usage: iotedgedev docker setup [OPTIONS]
+
+  Pull Edge runtime images from Microsoft Container Registry and push to
+  your specified container registry. Also, update config files to use
+  CONTAINER_REGISTRY_* instead of the Microsoft Container Registry. See
+  CONTAINER_REGISTRY environment variables.
+
+Options:
+  -h, --help  Show this message and exit.
+```
+
+## iotedgedev iothub
+
+```text
+Usage: iotedgedev iothub [OPTIONS] COMMAND [ARGS]...
+
+  Manage IoT Hub and IoT Edge devices
+
+Options:
+  -h, --help  Show this message and exit.
+
+Commands:
+  deploy   Create a deployment in IoT Hub
+  monitor  Monitor messages from IoT Edge device to IoT Hub
+  setup    Retrieve or create required Azure resources
+```
+
+## iotedgedev iothub deploy
+
+```text
+Usage: iotedgedev iothub deploy [OPTIONS]
+
+  Create a deployment in IoT Hub. For more information on how automatic deployments work see:
+  https://docs.microsoft.com/en-us/azure/iot-edge/module-deployment-monitoring
+
+Options:
+  -f, --file TEXT                 Specify the deployment manifest file  [default: config/deployment.amd64.json]
+  -n, --name TEXT                 Specify the name of the deployment that will be created in the IoT hub.  [required]
+  -p, --priority TEXT             Specify the deployment priority as positive integer. In the event that two or more
+                                  deployments are targeted at the same device, the deployment with the highest
+                                  numerical value for Priority will apply.  [required]
+  -t, --target-condition, --tc TEXT
+                                  Specify a target condition to determine which devices will be targeted with this
+                                  deployment. The condition is based on device twin tags or device twin reported
+                                  properties and should match the expression format. For example,
+                                  tags.environment='test' and properties.reported.devicemodel='4000x'. This property
+                                  can be set via this parameter or in the .env under
+                                  'IOTHUB_DEPLOYMENT_TARGET_CONDITION'  [default: ;required]
+  -dt, --device-tag TEXT          Specify the tag to be added to the device twin. 
+                                  For example, "{"environment":"dev"}". This property
+                                  can be set via this parameter or in the .env under
+                                  'DEVICE_TAGS'.
+  -h, --help                      Show this message and exit.
+```
+
+## iotedgedev iothub monitor
+
+```text
+Usage: iotedgedev iothub monitor [OPTIONS]
+
+  Monitor messages from IoT Edge device to IoT Hub
+
+Options:
+  -t, --timeout TEXT  Specify number of seconds to monitor for messages
+  -h, --help          Show this message and exit.
+```
+
+## iotedgedev iothub setup
+
+```text
+Usage: iotedgedev iothub setup [OPTIONS]
+
+  Retrieve or create required Azure resources
+
+Options:
+  --credentials <TEXT TEXT>...    Enter Azure Credentials (username password).
+  --service-principal <TEXT TEXT TEXT>...
+                                  Enter Azure Service Principal Credentials (username password tenant).
+  --subscription TEXT             The Azure Subscription Name or Id.  [required]
+  --resource-group-location [australiaeast|australiasoutheast|brazilsouth|canadacentral|canadaeast|centralindia|centralus|eastasia|eastus|eastus2|japanwest|japaneast|northeurope|northcentralus|southindia|uksouth|ukwest|westus|westeurope|southcentralus|westcentralus|westus2]
+                                  The Resource Group Location.  [required]
+  --resource-group-name TEXT      The Resource Group Name (Creates a new Resource Group if not found).  [required]
+  --iothub-sku [F1|S1|S2|S3]      The IoT Hub SKU.  [required]
+  --iothub-name TEXT              The IoT Hub Name (Creates a new IoT Hub if not found).  [required]
+  --edge-device-id TEXT           The IoT Edge Device Id (Creates a new Edge Device if not found).  [required]
+  -u, --update-dotenv             If True, the current .env will be updated with the IoT Hub and Device connection strings.  [default: False; required]
+  -h, --help                      Show this message and exit.
+```
+
+## iotedgedev simulator
+
+```text
+Usage: iotedgedev simulator [OPTIONS] COMMAND [ARGS]...
+
+  Manage IoT Edge simulator
+
+Options:
+  -h, --help  Show this message and exit.
+
+Commands:
+  modulecred  Get the credentials of target module such as connection string and certificate file path.
+  setup       Setup IoT Edge simulator. This must be done before starting
+  start       Start IoT Edge simulator
+  stop        Stop IoT Edge simulator
+```
+
+## iotedgedev simulator modulecred
+
+```text
+Usage: iotedgedev simulator modulecred [OPTIONS]
+
+  Get the credentials of target module such as connection string and
+  certificate file path.
+
+Options:
+  -l, --local             Set `localhost` to `GatewayHostName` for module to run on host natively.  [default: False]
+  -o, --output-file TEXT  Specify the output file to save the credentials. If the file exists, its content will be overwritten.
+  -h, --help              Show this message and exit.
+```
+
+## iotedgedev simulator setup
+
+```text
+Usage: iotedgedev simulator setup [OPTIONS]
+
+  Setup IoT Edge simulator. This must be done before starting
+
+Options:
+  -g, --gateway-host TEXT  GatewayHostName value for the module to connect.
+                           [default: <your hostname>]
+  -h, --help               Show this message and exit.
+```
+
+## iotedgedev simulator start
+
+```text
+Usage: iotedgedev simulator start [OPTIONS]
+
+  Start IoT Edge simulator. To start in solution mode, use `iotedgdev
+  simulator start -s [-v] [-b]`. To start in single module mode, use
+  `iotedgedev simulator start -i input1,input2 [-p 53000]`
+
+Options:
+  -u, --setup          Setup IoT Edge simulator before starting.  [default: False]
+  -s, --solution       Start IoT Edge simulator in solution mode using the deployment.json in config folder.  [default: False]
+  -v, --verbose        Show the solution container logs.  [default: False]
+  -b, --build          Build the solution before starting IoT Edge simulator in solution mode.  [default: False]
+  -f, --file TEXT      Specify the deployment manifest file. When `--build` flag is set, specify a deployment manifest template and it will be built.  [default: config\deployment.amd64.json]
+  -P, --platform TEXT  Specify the platform  [default: amd64]
+  -i, --inputs TEXT    Start IoT Edge simulator in single module mode using the specified comma-separated inputs of the target module, e.g., `input1,input2`.
+  -p, --port INTEGER   Port of the service for sending message.  [default: 53000]
+  -h, --help           Show this message and exit.
+```
+
+## iotedgedev simulator stop
+
+```text
+Usage: iotedgedev simulator stop [OPTIONS]
+
+  Stop IoT Edge simulator
+
+Options:
+  -h, --help  Show this message and exit.
+```
+
+## iotedgedev solution
+
+```text
+Usage: iotedgedev solution [OPTIONS] COMMAND [ARGS]...
+
+  Manage IoT Edge solutions
+
+Options:
+  -h, --help  Show this message and exit.
+
+Commands:
+  add        Add a new module to the solution
+  build      Build the solution
+  deploy     Deploy solution to IoT Edge device
+  e2e        Push, deploy, start, monitor
+  genconfig  Expand environment variables and placeholders in deployment manifest template file and copy to config folder
+  init       Create a new IoT Edge solution and provision Azure resources
+  new        Create a new IoT Edge solution
+  push       Push module images to container registry
+```
+
+## iotedgedev solution add
+
+```text
+Usage: iotedgedev solution add [OPTIONS] NAME
+
+  Add a new module to the solution, where NAME is the module name
+
+Options:
+  -t, --template [c|csharp|java|nodejs|python|csharpfunction]
+                                  Specify the template used to create the default module  [default: csharp]
+  -g, --group-id TEXT             (Java modules only) Specify the groupId  [default: com.edgemodule]
+  -h, --help                      Show this message and exit.
+```
+
+## iotedgedev solution build
+
+```text
+Usage: iotedgedev solution build [OPTIONS]
+
+  Build the solution
+
+Options:
+  -p, --push           Push module images to container registry  [default: False]
+  -d, --deploy         Deploy modules to Edge device using deployment.json in the config folder  [default: False]
+  -f, --file TEXT      Specify the deployment manifest template file  [default: deployment.template.json]
+  -P, --platform TEXT  Specify the platform  [default: amd64]
+  -h, --help           Show this message and exit.
+```
+
+## iotedgedev solution deploy
+
+```text
+Usage: iotedgedev solution deploy [OPTIONS]
+
+  Deploy solution to IoT Edge device
+
+Options:
+  -f, --file TEXT  Specify the deployment manifest file  [default: config\deployment.amd64.json]
+  -h, --help       Show this message and exit.
+```
+
+## iotedgedev solution e2e
+
+```text
+Usage: iotedgedev solution e2e [OPTIONS]
+
+  Push, deploy, start, monitor
+
+Options:
+  -h, --help  Show this message and exit.
+```
+
+## iotedgedev solution genconfig
+
+```text
+Usage: iotedgedev solution genconfig [OPTIONS]
+
+  Expand environment variables and placeholders in deployment manifest
+  template file and copy to config folder
+
+Options:
+  -f, --file TEXT      Specify the deployment manifest template file [default: deployment.template.json]
+  -P, --platform TEXT  Specify the platform  [default: amd64]
+  -h, --help           Show this message and exit.
+```
+
+## iotedgedev solution init
+
+```text
+Usage: iotedgedev solution init [OPTIONS]
+
+  Create a new IoT Edge solution and provision Azure resources
+
+Options:
+  -m, --module TEXT               Specify the name of the default module  [default: filtermodule]
+  -t, --template [c|csharp|java|nodejs|python|csharpfunction]
+                                  Specify the template used to create the default module  [default: csharp]
+  -g, --group-id TEXT             (Java modules only) Specify the groupId  [default: com.edgemodule]
+  -h, --help                      Show this message and exit.
+```
+
+## iotedgedev solution new
+
+```text
+Usage: iotedgedev solution new [OPTIONS] NAME
+
+  Create a new IoT Edge solution, where NAME is the solution folder name.
+  Use "." as NAME to create in the current folder.
+
+Options:
+  -m, --module TEXT               Specify the name of the default module  [default: filtermodule]
+  -t, --template [c|csharp|java|nodejs|python|csharpfunction]
+                                  Specify the template used to create the default module  [default: csharp]
+  -g, --group-id TEXT             (Java modules only) Specify the groupId  [default: com.edgemodule]
+  -h, --help                      Show this message and exit.
+```
+
+## iotedgedev solution push
+
+```text
+Usage: iotedgedev solution push [OPTIONS]
+
+  Push module images to container registry
+
+Options:
+  -d, --deploy         Deploy modules to Edge device using deployment.json in the config folder  [default: False]
+  --no-build           Inform the push command to not build module images before pushing to container registry  [default: False]
+  -f, --file TEXT      Specify the deployment manifest template file  [default: deployment.template.json]
+  -P, --platform TEXT  Specify the platform  [default: amd64]
+  -h, --help           Show this message and exit.
+```
+
+
+## iotedgedev solution tag
+
+```text
+Usage: iotedgedev solution tag [OPTIONS]
+
+  Adds tags to device twin for automatic deployments
+
+Options:
+  -t, --tags TEXT     Specify the tag to be added to the device twin. 
+                      For example, "{"environment":"dev"}". This property
+                      can be set via this parameter or in the .env under
+                      'DEVICE_TAGS'.  [default: ;required]
+  -h, --help          Show this message and exit.
+```

s/docs/Command-Tips.md

@@ -0,0 +1,51 @@
+### Setup Container Registry
+
+You can also use IoT Edge Dev Tool to host the IoT Edge runtime from your own Azure Container Registry or a local container registry. Set the `.env` values for your container registry and run the following command. It will pull all the IoT Edge containers from Microsoft Container Registry, tag them and push them to the container registry you have specified in `.env`. 
+
+> Use 'sudo' for Linux/Raspberry Pi
+
+```
+iotedgedev docker setup-registry
+```
+
+
+### View Docker Logs
+
+#### Show Logs
+IoT Edge Dev Tool also includes a "Show Logs" command that will open a new command prompt for each module it finds in your IoT Edge config. Just run the following command:
+
+> Note: I haven't figured out how to launch new SSH windows in a reliable way.  It's in the backlog.  For now, you must be on the desktop of the machine to run this command.
+
+```
+iotedgedev docker log --show
+```
+
+You can configure the logs command in the `.env` file with the `LOGS_CMD` setting.  The `.env` file provides two options, one for [ConEmu](https://conemu.github.io/) and one for Cmd.exe.
+
+#### Save Logs
+
+You can also output the logs to the LOGS_PATH directory.  The following command will output all the logs and add them to an `edge-logs.zip` file that you can send to the Azure IoT support team if they request it.
+
+```
+iotedgedev docker log --save
+```
+
+#### Both Show and Save Logs
+
+Run the following to show and save logs with a single command
+
+```
+iotedgedev docker log --show --save
+```
+
+
+### Local Docker Registry Setup
+
+Instead of using a cloud based container registry, you can use a local Docker registry. Here's how to get it setup.
+
+1. Set `CONTAINER_REGISTRY_SERVER` in `.env` file to `localhost:5000`. You can enter a different port if you'd like to.
+1. Add `localhost:5000` and `127.0.0.1:5000` to Docker -> Settings -> Daemon -> Insecure Registries
+
+> In the latest IoT Edge Dev Tool, Step 2 above hasn't been required. But, if you run into issues, you may want to try adding those Insecure Registries.
+
+IoT Edge Dev Tool will look for `localhost` in your setting and take care of the rest for you.

s/docs/Edge-Device-Setup.md

@@ -0,0 +1,23 @@
+IoT Edge Dev Tool is intended to help with IoT Edge development and doesn't necessarily need to be taken on as a dependency in production or integration environments, where you'll likely want to use the IoT Edge runtime directly. Please check below documents for the instructions on setting up IoT Edge runtime:
+- [Linux X64](https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-linux)
+- [Linux ARM32](https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-linux-arm)
+- [Windows with Windows container](https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-windows-with-windows)
+- [Windows with Linux container](https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-windows-with-linux)
+- [IoT Core](https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-core)
+
+Having said that, there's nothing stopping you from deploying IoT Edge Dev Tool to your IoT Edge device. It may be helpful if you want to run the `iotedgedev docker clean` command to clean up Docker containers and images. Or if you want to run `iotedgedev docker log --show` to see all the log files on the device or `iotedgedev docker log --save` to output to the LOGS_PATH directory.
+
+> Please note that you will need .NET Core SDK 2.1 to add C# modules and C# Function modules on a Raspberry Pi. Check [Manual Dev Machine Setup](manual-dev-machine-setup#c-module-and-c-azure-functions-module) to learn how to install.
+
+### Raspberry Pi
+
+##### Config Changes
+If you are running on Raspberry Pi you need to use the arm32v7 Dockerfile. Open `deployment.template.json`, find the JSON dictionary for `filtermodule`, and replace `"image": "${MODULES.filtermodule.amd64}",` with `"image": "${MODULES.filtermodule.arm32v7}",`
+
+##### Environment Variable Change
+
+Open your `.env` file and add `arm32v7` to your `ACTIVE_DOCKER_PLATFORMS` setting. This will tell the IoT Edge Dev Tool to also build the arm32v7 images.
+
+```
+ACTIVE_DOCKER_PLATFORMS="amd64,arm32v7"
+```

s/docs/Home.md

@@ -0,0 +1,10 @@
+Welcome to the IoT Edge Dev Tool wiki!
+
+The **IoT Edge Dev Tool** greatly simplifies [Azure IoT Edge](https:/azure.microsoft.com/en-us/services/iot-edge/) development down to simple commands driven by environment variables.
+
+ - It gets you started with IoT Edge development with the [IoT Edge Dev Container](quickstart-with-iot-edge-dev-container) and IoT Edge solution scaffolding that contains a default module and all the required configuration files.
+ - It speeds up your inner-loop dev (dev, debug, test) by reducing multi-step build & deploy processes into one-line CLI commands as well as drives your outer-loop CI/CD pipeline. _You can use all the same commands in both stages of your development life-cycle._
+
+## Issues
+
+Please use the [GitHub issues page](https://github.com/azure/iotedgedev/issues) to report any issues.