fix: storage keys cross-version compat#860
Merged
ketkimnaik merged 2 commits intoJul 14, 2026
Merged
Conversation
HangyiWang
approved these changes
Jul 14, 2026
Member
|
Hi @ketkimnaik, you can pull the latest preview branch to fix the CI Build error. See #853 if needed. |
ketkimnaik
added a commit
that referenced
this pull request
Jul 18, 2026
* feat: Add adu tls support (#846) * Add tls support- first draft * Fix linting error * chore: Regenerate deviceupdate dataplane SDK for 2026-06-01 API via AutoRest Use AutoRest 3.9.2 + @autorest/python@5.19.0 against: specification/deviceupdate/data-plane/Microsoft.DeviceUpdate/stable/2026-06-01/deviceupdate.json Key changes from 2022-10-01: - api_version updated to 2026-06-01 throughout all operations - Added DownloadSecurity enum (https/http) - Added download_security field to Deployment model * feat: Add --download-security parameter to adu device deployment create * fix: patch IO isinstance check * fix: patch autorest generator bugs * Updated the help text to be more precise. * Fix mismatched format * fix: E501 line too long in params help text --------- Co-authored-by: Ketki <ketkinaik@microsoft.com> * fix: storage keys cross-version compat (#860) * fix: storage keys cross-version compat * fix: bump wheel to 0.45.1 for CI linter --------- Co-authored-by: Ketki <ketkinaik@microsoft.com> * fix: storage keys SDK compat (#861) Co-authored-by: Ketki <ketkinaik@microsoft.com> * fix: storage keys SDK compat (#862) Co-authored-by: Ketki <ketkinaik@microsoft.com> --------- Co-authored-by: Ketki <ketkinaik@microsoft.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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).