microsoft / microsoft/AzureStorageExplorer
Keep a consistent behavior between deleting one ADLS Gen2 blob and one regular blob with snapshots
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Storage Explorer Version: 1.14.1
Build: 20200710.5
Branch: hotfix/1.14.1
Platform/OS: Windows 10/ Linux Ubuntu 18.04/ macOS Catalina
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:
- Expand one ADLS Gen2 storage account -> Try to delete one blob with snapshots -> Check the Activity log.
- Expand one storage account -> Try to delete one blob with snapshots -> Check the Activity log.
Expect Experience:
Keep a consistent behavior.
Actual Experience:
Display an inconsistent behavior.
-
The activity shows below when trying to delete one ADLS Gen2 blob with snapshots.
-
The activity shows below when trying to delete one regular blob with snapshots.
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 two deletion flows described for an ADLS Gen2 blob and a regular blob with snapshots, then compare their Activity log entries. Done means both operations display consistent behavior; the issue does not specify which behavior should be preferred.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100