{Interactive} Pass the cli_ctx when it calls `handle_exception`
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
When an exception is thrown and handled, it may also ask for the LLM for the suggestion to fix the error. To make that work, we need to pass the cli_ctx when we call handle_exception directly in the interactive mode. The feature is enabled/disabled separately by a configuration though. See this PR for what is done to show the suggestion when an error occurs. https://github.com/Azure/azure-cli/pull/27801
General Guidelines
- [x] Have you run
azdev style <YOUR_EXT>locally? (pip install azdevrequired) - [x] Have you run
python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required)
For new extensions:
- [ ] My extension description/summary conforms to the Extension Summary Guidelines.
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.
Hi @kceiw, Usually we only allow pull requests to be submitted to the main branch, please double check your pull request target branch error_recovery_integrated_with_gpt.
️✔️Azure CLI Extensions Breaking Change Test
️✔️Non Breaking Changes
Hi @kceiw, Please write the description of changes which can be perceived by customers into HISTORY.rst. If you want to release a new extension version, please update the version in setup.py as well.
Hi @kceiw, Since the current milestone time is less than 7 days, this pr will be reviewed in the next milestone.
Interactive
With the latest changes in the related PR, we don't need the change in this PR anymore. We just need to have azure-cli-core to enable this feature.
We still need the change in this PR. Re-open it.