[Core] Add spinner progress bar for long running operation#17262
[Core] Add spinner progress bar for long running operation#17262
Conversation
|
Core |
| class IndeterminateProgressBar: | ||
| """ Define progress bar update view """ | ||
| def __init__(self, cli_ctx, message="Running"): | ||
| self.cli_ctx = cli_ctx |
There was a problem hiding this comment.
Consider dropping cli_ctx reference if it is unused.
There was a problem hiding this comment.
It is used in L181 to get progress controller
|
I compared the implement before and found that the original way support spinner already. There's just a bug winthin azure-cli/src/azure-cli-core/azure/cli/core/__init__.py Lines 118 to 124 in 7d0dd03 LRO calls To support spinning for LRO, we only need to log |
Yes, there is an issue in previous design. Here I don't use add() because I want to expand progress bar capability with update_progress(), which could have more progress bar UI. |
Co-authored-by: kai ru <69238381+kairu-ms@users.noreply.github.com>
Description
This PR is one part for progress bar project.

As we already in beta version for several months, I plan to move indeterminate progress bar with spinner to all long running operation in azure cli as shown below:
But I have to mention for commands like
network vnet create, which is long running operation, but not hornor CLILongRunningOperationclass, will not have progress bar.Testing Guide
az storage account createaz vm createHistory Notes
[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.