microsoft / microsoft/AzureStorageExplorer

Storage Explorer should be consistent with Azure Portal in showing blob type for different Storage account types

Open
#703 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

:gear: blobs :gear: data transfer :gear: storage accounts
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Storage Explorer Version: 1.4.2
Platform/OS Version: Windows
Architecture: ia32
Regression From: Unsure

Steps to Reproduce:
  1. Highlight a Storage account
  2. Click on Upload Files
  3. Click on the Blob type drop down list
Expected Experience:

Standard Blob accounts should only allow Block Blobs and Append Blobs but not Page Blobs
Premium SV2 Accounts should only allow Page Blobs but not Block Blobs or Append Blobs
Premium Blob accounts should only allow Block Blobs and Append Blobs but not Page Blobs

Actual Experience:

Standard Blob accounts allows Page Blobs
Premium SV2 Accounts allows Block or Append Blobs
Premium Blob accounts allows Page Blobs

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 reproducing the issue in the Upload Files dialog and inspect how the Blob type drop-down is populated for each storage account type. Done means Standard Blob accounts show only Block and Append Blobs, Premium SV2 accounts show only Page Blobs, and Premium Blob accounts show only Block and Append Blobs.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
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.