Closed vilit1 closed 1 year ago
Do we need a history update for this? It looks like we added at least one param (user_identity)
I will add one when it is closer to actually being merged in (I hate merge conflicts with history)
Here is the blurb that I will put:
**Digital Twins**
* Addition of User Assigned Identities for data history connections. The command `az dt data-history connection create adx` now can take an extra parameter `--mi-user-assigned` to use an associated User Assigned Identity for the connection creation rather than the system assigned identity for the Digital Twin.
* Some minor improvements to command documentation involving managed identities.
Goals of this pr:
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
dev
ormain
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
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..pylintrc
and.flake8
rules? 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).