microsoft / microsoft/vscode-azureresourcegroups

The newly created blob container doesn't show in "Blob Containers" node if creating it from command palette

Open
#1,011 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🐛bug AT-CTI
Dominant language
TypeScript
Stars
78
Forks
55
Avg merge
16h 49m
Merged PRs (30d)
139

Description

OS: All
Build Version: Azure Resources extension v0.10.2 & Azure Storage extension v0.16.1
Regression: Previous Release (v0.9.9)

Repro Steps:

  1. Create a storage account.
  2. Expand the above storage account -> Expand "Blob Containers" node.
  3. Create a blob container from command palette.
  4. Check whether the newly created blob container shows in "Blob Containers" node.

Expect:
The newly created blob container shows in "Blob Containers" node.

Actual:
The newly created blob container doesn't show in "Blob Containers" node.

More Info:

  1. This issue also reproduces when creating or deleting blob container/file share/queue/table from command palette.
  2. Refreshing "Azure view" can fix this issue.
  3. This issue does not reproduce on Azure Resources extension v0.9.9.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the command-palette handlers for creating and deleting blob containers, file shares, queues, and tables, then inspect how the Azure view refreshes its resource nodes. Reproduce the issue with a storage account and compare command-palette operations with a manual Azure view refresh. Done means each newly created or deleted resource appears correctly without manually refreshing the view.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript
Domain
cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.