The Digital Twin commands will now use the newest API 2023-01-31.
Added new options for creating a data history connection and deleting one. The create command, az dt data-history connection create adx, now supports adding two separate tables for relationship lifecycle events and twin lifecycle events, recording property and item removals, and adding the new default for the generic table name (now known as property event table). The delete command, az dt data-history connection delete, now supports a clean parameter which will do a best-effort attempt to clean connection creation artifacts.
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
Intent for Production
[ ] It is expected that pull requests made to default or core branches such as dev or main are of production grade. Corollary to this, any merged contributions to these branches may be deployed in a public release at any given time. By checking this box, you agree and commit to the expected production quality of code.
Basic expectations
[ ] If introducing new functionality or modified behavior, are they backed by unit and/or integration tests?
[ ] In the same context as above are command names and their parameter definitions accurate? Do help docs have sufficient content?
[ ] Have all the relevant unit and integration tests pass? i.e. pytest <project root> -vv. Please provide evidence in the form of a screenshot showing a succesful run of tests locally OR a link to a test pipeline that has been run against the change-set.
[ ] Have linter checks passed using the .pylintrc and .flake8 rules? Look at the CI scripts for example usage.
[ ] Have extraneous print or debug statements, commented out code-blocks or code-statements (if any) been removed from the surface area of changes?
[ ] Have you made an entry in HISTORY.rst which concisely explains your user-facing feature or change?
Azure IoT CLI maintainers reserve the right to enforce any of the outlined expectations.
A PR is considered ready for review when all basic expectations have been met (or do not apply).
vilit1
commented
1 year ago
Note 12/27: only works in North Europe so far.
Note 1/10: bug bash planned for 1/31
Add new functionality for create and delete:
History: Digital Twins
az dt data-history connection create adx, now supports adding two separate tables for relationship lifecycle events and twin lifecycle events, recording property and item removals, and adding the new default for the generic table name (now known as property event table). The delete command,az dt data-history connection delete, now supports a clean parameter which will do a best-effort attempt to clean connection creation artifacts.This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Thank you for contributing to the IoT extension!
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
Intent for Production
devormainare of production grade. Corollary to this, any merged contributions to these branches may be deployed in a public release at any given time. By checking this box, you agree and commit to the expected production quality of code.Basic expectations
pytest <project root> -vv. Please provide evidence in the form of a screenshot showing a succesful run of tests locally OR a link to a test pipeline that has been run against the change-set..pylintrcand.flake8rules? Look at the CI scripts for example usage.Azure IoT CLI maintainers reserve the right to enforce any of the outlined expectations.
A PR is considered ready for review when all basic expectations have been met (or do not apply).