microsoft / microsoft/vscode-azureresourcegroups
The "recently used" label does not point to the correct Microsoft account that was most recently used to create the resource group
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 55
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 139
Description
OS: All
Build Version: 0.9.9
Repro Steps:
- Sign in with two Microsoft accounts which have the same subscription.
- F1 -> Select "Create Resource group..." -> Select the subscription -> select a location for new resource.
- Repeat the same process to create another resource group by selecting the same subscription of a different Microsoft account
- F1 -> Select "Create Resource group...".
- Check whether the "recently used" label points to the correct Microsoft account that was most recently used to create the resource group.
Expect:
The "Recently used" label points to the correct Microsoft account that was most recently used to create the resource group.
Actual:
The "Recently used" label does not point to the correct Microsoft account that was most recently used to create the resource group.
More Info:
This issue does not reproduce when logged in with one Microsoft account.
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 reproducing the issue through the F1 command and the "Create Resource group..." flow with two Microsoft accounts sharing a subscription. Trace how the recently used account is selected and stored after each resource-group creation. Done means the label identifies the account most recently used to create the resource group.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100