feat: update for assets and asset endpoint profiles to support new api version

[vilit1]

Lots of things:

• new api version
• assets changes
• asset datapoint/event changes
• asset endpoint changes

---

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 Azure IoT Operations tooling!

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 Operations 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).

[digimaun]

Was this a copy paste from? https://github.com/Azure/azure-iot-ops-cli-extension/blob/feature/0.7.0/azext_edge/tests/edge/orchestration/resources/conftest.py#L22,

[vilit1]

oh no you found it - yes.

will prob move it out after your review

[vilit1]

will fix this in the next pr

[digimaun]

Can you expand on this? It's odd that assets show will set the self.update_ops attribute?

[digimaun]

Reviewing further, looks like non show/list operations assume self.update_ops to be set with the expected operation instance, and the show function is responsible for setting the attribute.

[vilit1]

This is a set up for discovered assets so the same update/list/etc methods can be reused since they share almost all properties.

Flow will be (given a name):

1. try to get the asset - set the update ops as the asset ops
2. if 1 fails, try to get the discovered asset - set the update ops as the discovered asset ops
3. do the update/etc with the update ops

[vilit1]

will update this as I implement/do things with discovered