microsoft / microsoft/vscode-azureresourcegroups
The newly created resource group only shows in one subscription node when two identical subscription nodes are expanded
Open
Nobody has claimed this yet.
AT-CTI
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 55
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 139
Description
OS: All
Build Version: v0.10.2
Repro Steps:
- Sign in with two Microsoft accounts which have identical subscriptions.
- Select two identical subscriptions from 2 Microsoft accounts.
- Expand the 2 subscription nodes.
- Group the resources by "Resource Group".
- Create one resource group.
- Check whether the newly created resource group shows in two identical subscription nodes.
Expect:
The newly created resource group shows in two identical subscription nodes.
Actual:
The newly created resource group only shows in one subscription node.
More Info:
- The newly created resource group shows in two identical subscription nodes after refreshing Azure Resources view.
- This issue also reproduces when deleting resource group.
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
Reproduce the issue in the Azure Resources view with two accounts that have identical subscriptions, then compare the immediate create and delete behavior with the result after refreshing. Trace the resource-group update path and ensure both expanded subscription nodes reflect each operation without requiring a refresh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- cloud, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100