The Azure IoT Edge Dev Tool greatly simplifies your Azure IoT Edge development process. It has everything you need to get started and helps with your day-to-day Edge development.
This checklist is used to make sure that common guidelines for a pull request are followed.
[ ] Versions update reflected in all places (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
[ ] Pull request includes test coverage for the included changes
[x] Documentation is updated for the included changes
General guidelines
[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR.
Description
Fixes #552
This PR adds an optional flag to iotedgedev iothub setup to also create an edge-enabled virtual machine.
It uses the deployment template available at https://github.com/Azure/iotedge-vm-deploy - it will be incrementally applied.
Additional information
The user will be prompted for an ssh key - if there is none, one will be created (id_rsa_iotedgedev in the ~/.ssh directory).
Known issues
It is not possible to pass a name for the virtual machine to the deployment template, one will be created randomly.
The template sets up a default-allow-22 inbound port rule - this is not ideal.
The output of the template is not captured, the user has to check the portal for the login details
Checklist
This checklist is used to make sure that common guidelines for a pull request are followed.
General guidelines
Description
Fixes #552
This PR adds an optional flag to
iotedgedev iothub setup
to also create an edge-enabled virtual machine. It uses the deployment template available at https://github.com/Azure/iotedge-vm-deploy - it will be incrementally applied.Additional information
The user will be prompted for an ssh key - if there is none, one will be created (
id_rsa_iotedgedev
in the~/.ssh
directory).Known issues
default-allow-22
inbound port rule - this is not ideal.