New Capture Stderr - Githubissues

Original pr: https://github.com/Azure/azure-iot-cli-extension/pull/646

The new method for the catch stderr:

allow for setting capture_stderr on init or invoke command; invoke command will overwrite init settings
if capture_stderr is False, the embedded cli follows the original way (it will print out the stderr but not throw errors caused by it)
if capture_stderr is True, the embedded cli will catch the stderr (errors will not be printed during invocation) but any error will be raised after for better error handling (and print it to console if we code it to do so).
Goal is to have True become default

Changed some tests to reflect the errors raised - tests now look for more specific errors rather than failure. Also added some error handling to message endpoint and route

Only some tests are using the new functionality.

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

[ ] 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).

Azure / azure-iot-cli-extension

New Capture Stderr #667

General Guidelines