azure-iot-cli-extension Iot Central api-version parameter deprecated and some APIs support

Iot Central api-version parameter deprecated and some APIs support

Open HangyiWang opened this issue 1 year ago • 1 comments

--api-version parameter will be deprecated and ignored. The IoT Central API will alway call latest GA version or latest preview version (if any API only exists in preview).
Add support for enrollment groups CRUD.
- az iot central enrollment-group
  - az iot central enrollment-group list
  - az iot central enrollment-group show
  - az iot central enrollment-group create
  - az iot central enrollment-group delete
  - az iot central enrollment-group update
- az iot central enrollment-group x509
  - az iot central enrollment-group x509 create
  - az iot central enrollment-group x509 show
  - az iot central enrollment-group x509 delete
  - az iot central enrollment-group x509 verify
  - az iot central enrollment-group x509 generate
Add support for scheduled jobs CRUD.
- az iot central scheduled-job
  - az iot central scheduled-job list
  - az iot central scheduled-job show
  - az iot central scheduled-job create
  - az iot central scheduled-job delete
  - az iot central scheduled-job update
  - az iot central scheduled-job list-jobs

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] 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

[x] 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

[x] If introducing new functionality or modified behavior, are they backed by unit and/or integration tests?
[x] In the same context as above are command names and their parameter definitions accurate? Do help docs have sufficient content?
[x] 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.
[x] Have linter checks passed using the .pylintrc and .flake8 rules? Look at the CI scripts for example usage.
[x] Have extraneous print or debug statements, commented out code-blocks or code-statements (if any) been removed from the surface area of changes?
[x] 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).

cli int tests unit1

cli int tests int1

Aug 29 '22 16:08 HangyiWang

Passed unit tests and integration tests again.

Aug 31 '22 19:08 HangyiWang

test

Sep 14 '22 18:09 vilit1

Taking a look into why the merge pipeline is hanging. We recently made some conformance changes that require comments from team members for builds of forks - have a hunch that's causing something to block here.