microsoft / microsoft/vscode-azureresourcegroups
[CoR] [Suggestion] Provide estimated remaining time for long-running deployment workflows
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 55
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 139
Description
OS: Win11 x64
Build Version: 0.12.8-alpha.0
VS Code Version: Version: 1.137.0
Repro Steps:
- Create and deploy a CoR project
- Observe the deployment workflow during a long-running deployment
Expect:
The deployment workflow should provide an estimated completion time or duration for the remaining deployment activities.
Actual:
During a long-running deployment, the remaining steps were visible, but there was no indication of how long the remaining work would take. It was difficult to determine whether the deployment would finish in minutes, hours, or require additional user intervention.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the deployment workflow described in the reproduction steps and identify where its remaining activities and progress are exposed. Determine what timing data is available and how an estimate should be presented; done means a long-running deployment communicates its estimated remaining duration or completion time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100