iotedgedev 3.3.4__zip → 3.3.5__zip

s/tests/test_iotedgedev_solution_init.py

@@ -0,0 +1,34 @@
+import os
+import shutil
+import uuid
+from unittest import mock
+from .utility import (runner_invoke)
+
+
+def test_solution_init_without_name():
+    result = runner_invoke(['solution', 'init'], True)
+
+    assert "Directory is not empty" in result.output
+
+
+def test_solution_init_with_invalid_name_non_empty_dir():
+    dirname = f'test-{uuid.uuid4()}'
+    os.makedirs(f'{dirname}/empty_dir')
+
+    result = runner_invoke(['solution', 'init', dirname], True)
+
+    assert "Directory is not empty" in result.output
+    shutil.rmtree(dirname, ignore_errors=True)
+
+
+def test_solution_init_with_valid_name():
+    dirname = f'test-{uuid.uuid4()}'
+
+    # Mock calls to additional commands, to avoid triggering user prompts
+    with mock.patch('iotedgedev.utility.Utility.call_proc') as mock_call_proc:
+        result = runner_invoke(['solution', 'init', dirname], True)
+
+    assert 'AZURE IOT EDGE SOLUTION CREATED' in result.output
+    mock_call_proc.assert_called_with(["iotedgedev", "iothub", "setup", "--update-dotenv"])
+    assert mock_call_proc.call_count == 2
+    shutil.rmtree(dirname, ignore_errors=True)

s/.git/logs/refs/remotes/origin/eliises/add-device-tagging-docs

@@ -1 +0,0 @@
-0000000000000000000000000000000000000000 89935ca2b03964ef69cbccb1b8e5815ca25ec62d Ubuntu <cloudtest@fd6fd2d8c000000.p5rt4sl1n0gu1ozd445c4dptsd.bx.internal.cloudapp.net> 1648752750 +0000	fetch --force --tags --prune --prune-tags --progress --no-recurse-submodules origin: storing head

s/.git/refs/remotes/origin/eliises/add-device-tagging-docs

@@ -1 +0,0 @@
-89935ca2b03964ef69cbccb1b8e5815ca25ec62d

s/.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,16 +0,0 @@
----
-name: Bug report
-about: Create a issue to help us improve
----
-
-<!-- Fill in the information needed -->
-- iotedgedev Version:
-- Python Version:
-- Pip Version:
-- Development machine OS Version:
-- IoT Edge device OS Version:
-
-Steps to Reproduce:
-
-1.
-2.

s/.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,7 +0,0 @@
----
-name: Feature request
-about: Suggest an idea for IoT Edge and IoT Edge development tools
-
----
-
-<!-- Describe the feature you'd like. -->

s/docs/Home.md

@@ -1,10 +0,0 @@
-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.

s/docs/Manual-Dev-Machine-Setup.md

@@ -1,77 +0,0 @@
-Here is what you need to do to get Azure IoT Edge Dev Tool (aka `iotedgedev`) running on your dev machine manually instead of using the IoT Edge Dev Container.
-
-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.
-
-1. Install **[Docker](https://docs.docker.com/engine/installation/)**
-    - Windows    
-        - Be sure to check whether you are running in Linux container mode or Windows container mode.
-    - Linux
-        - We've seen some issues with docker.io. If Edge doesn't run for you, then try installing Docker CE directly instead of via docker.io. Use the [CE install steps](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).
-        - By default, you need `sudo` to run `docker` commands. If you want to avoid this, please follow the [post-installation steps for Linux](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user).
-        
-1. Install **Python 2.7+ or Python 3.6+** and **pip** (Python 3.6 is recommended)
-    - Windows: [Install from Python's website](https://www.python.org/downloads/)
-    - Linux: `sudo apt install python-pip` or `sudo apt install python3-pip`
-    - macOS: The OpenSSL used by the system built-in Python is old and vulnerable. Please use Python installed with [Homebrew](https://docs.brew.sh/Homebrew-and-Python)
-    
-1. Install **[Azure CLI 2.0](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)**
-
-1. Install **[Azure CLI IoT extension](https://github.com/Azure/azure-iot-cli-extension/)**
-
-    - New Install: `az extension add --name azure-iot`
-    - Update Install: `az extension update --name azure-iot`
-
-1. (Python < 3.5 only) Install **[Node.js](https://nodejs.org/en/download/)** and the **`iothub-explorer`** package
-
-    - uamqp, which is needed by Azure CLI IoT extension for monitoring messages, is not supported in Python < 3.5. For Python < 3.5 users, please install [Node.js](https://nodejs.org/en/download/) and the `iothub-explorer` Node.js package: `npm i -g iothub-explorer`
-
-1. (Raspberry Pi only) Install extra system dependencies
-
-    ```
-    sudo apt-get install python2.7-dev libffi-dev libssl-dev -y
-    ```
-
-1. (Linux only) Install [Docker Compose](https://docs.docker.com/compose/)
-
-    ```
-    pip install -U docker-compose
-    ```
-
-1. Install **`iotedgedev`**
-
-    > You do not need to run this on the Edge device. See the [Edge Device Setup](edge-device-setup) page for more information on setting up your Edge device.
-
-    > You can also run under a Python Virtual Environment.  See the [Python Virtual Environment Setup](python-virtual-environment-setup) instructions page for details on how to set that up.
-
-    > There is a known dependency conflict between `iotedgedev` and now-deprecated `azure-iot-edge-runtime-ctl`. Please make sure you have uninstalled `azure-iot-edge-runtime-ctl` before installing `iotedgedev`: `pip uninstall azure-iot-edge-runtime-ctl `, or use a clean virtual environment.
-
-    ```
-    pip install -U iotedgedev
-    ```
-
-1. Install module dependencies
-    ##### C# module and C# Azure Functions module
-    Install **[.NET Core SDK](https://www.microsoft.com/net/download)**.
-    > You need .NET Core SDK 2.1 or later to run it on ARM. There is no official document on installing .NET Core SDK on ARM yet, but you can follow the [ARM32v7 Dockerfile](https://github.com/dotnet/dotnet-docker/blob/master/src/sdk/3.1/buster/arm32v7/Dockerfile).
-    
-    ##### Python module
-    1. Install **[Git](https://git-scm.com/)**
-    2. Install **[Cookiecutter](https://github.com/audreyr/cookiecutter)**
-    ```
-    pip install -U cookiecutter
-    ```
-
-    ##### Node.js module
-    1. Install **[Node.js](https://nodejs.org/en/download/)**
-    2. Install **[Yeoman](http://yeoman.io/)** and **[Azure IoT Edge Node.js module generator](https://github.com/Azure/generator-azure-iot-edge-module)** packages
-    ```
-    npm i -g yo generator-azure-iot-edge-module
-    ```
-
-    ##### Java module
-    1. Install **[JDK](https://www.oracle.com/technetwork/java/javase/downloads/index.html)**
-    1. Install **[Maven](https://maven.apache.org/)**
-
-1. Follow the [Usage Wiki](usage) to learn the usage of IoT Edge Dev Tool

s/docs/Quickstart-with-IoT-Edge-Dev-Container.md

@@ -1,145 +0,0 @@
-Here is the absolute fastest way to get IoT Edge Dev Tool (aka `iotedgedev`) running on your dev machine with the IoT Edge Dev Container.
-
-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. 
-
-1. **Install [Docker CE](https://docs.docker.com/install/)**
-
-    - For Windows, please follow [the document](https://docs.docker.com/docker-for-windows/#shared-drives) to open Docker Settings and setup a Shared Drive.
-    - For macOS, please follow [the document](https://docs.docker.com/docker-for-mac/#file-sharing) to choose local directories to share with your containers.
-
-
-1. **Run the IoT Edge Dev Container**
-
-    Before you run the container, you will need to create a local folder to store your IoT Edge solution files.
-    
-    **Windows**
-    ```
-    mkdir c:\temp\iotedge
-    docker run -ti -v /var/run/docker.sock:/var/run/docker.sock -v c:/temp/iotedge:/home/iotedge microsoft/iotedgedev
-    ```
-
-    **Linux**
-    ```
-    sudo mkdir /home/iotedge
-    sudo docker run -ti -v /var/run/docker.sock:/var/run/docker.sock -v ~/iotedge:/home/iotedge microsoft/iotedgedev
-    ```
-
-    **macOS**
-    ```
-    mkdir ~/iotedge
-    docker run -ti -v /var/run/docker.sock:/var/run/docker.sock -v ~/iotedge:/home/iotedge microsoft/iotedgedev
-    ```
-
-1. **Initialize IoT Edge solution and setup Azure resources**
-
-    `iotedgedev init`
-
-    > `iotedgedev init` will create a solution 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:
-
-    ```
-        │  .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
-    ```
-
-    2. Open `.env` file, you will see the `IOTHUB_CONNECTION_STRING` and `DEVICE_CONNECTION_STRING` environment variables filled correctly.
-    3. Open `deployment.template.json` file   
-        1. You will see below section in the modules section:
-
-        ```
-        "filtermodule": {
-            "version": "1.0",
-            "type": "docker",
-            "status": "running",
-            "restartPolicy": "always",
-            "settings": {
-                "image": "${MODULES.filtermodule}",
-                "createOptions": ""
-            }
-        }
-        ```
-
-        2. Two default routes are added:
-        
-        ```
-        "routes": {
-            "sensorTofiltermodule": "FROM /messages/modules/tempSensor/outputs/temperatureOutput INTO BrokeredEndpoint(\"/modules/filtermodule/inputs/input1\")",
-            "filtermoduleToIoTHub": "FROM /messages/modules/filtermodule/outputs/* INTO $upstream"
-        }
-        ```
-
-    4. You will see privacy statement like below:
-
-        ```
-        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>
-
-1. **Build IoT Edge module images**
-
-    `sudo iotedgedev build`
-
-    > This step will build user modules in deployment.template.json targeting amd64 platform. You can use the `--file` and `--platform` parameters to change this behavior.
-
-    <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>
-
-1. **Setup and start the IoT Edge Simulator to run the solution**
-
-    `sudo iotedgedev start --setup --file config/deployment.amd64.json`
-
-    > IoT Edge Simulator does not support running Python and C modules yet. You'll need IoT Edge Runtime to run your Python and C modules.
-
-    <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 `sudo docker ps`, you will see your modules running as well as an edgeHubDev container
-
-    </details>
-
-1. **Monitor messages sent from IoT Edge Simulator to IoT Hub**
-
-    `iotedgedev monitor`
-
-    <details>
-    <summary>More information</summary>
-
-    1. You will see your expected messages sending to IoT Hub
-
-    </details>

s/pull_request_template.md

@@ -1,9 +0,0 @@
-## iotedgedev Pull Request Checklist
-
-- [ ] Versions updated (both __init__.py files, CHANGELOG, setup.py, setup.cfg)
-- [ ] Unit tests pass locally
-- [ ] Quickstart steps locally validated
-- [ ] Passes unit tests in CICD pipeline (green on Github pipeline)
-- [ ] Pypi RC version passes Edge CICD pipeline validation for cross-tool validation
-
-## Additional comments

s/tests/assets/test_solution_shared_lib/layered_deployment.no_modules.template.json

@@ -1,12 +0,0 @@
-{
-  "content": {
-    "modulesContent": {
-      "$edgeAgent": {},
-      "exampleModule": {
-        "properties.desired": {
-          "foo": "bar-${EDGE_RUNTIME_VERSION}"
-        }
-      }
-    }
-  }
-}