microsoft / microsoft/AzureStorageExplorer
Because Storage Explorer is using data plane deletes, ARM locks on containers are not respected
Open
Nobody has claimed this yet.
:grey_question: investigate
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
- Create container
- Put an ARM lock on it
- Try deleting in Storage Explorer
Actual behavior:
Container is deleted
Expected behavior:
Not sure. We need to talk to platform team about what the think about this situation.
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 Storage Explorer by creating a container, applying an ARM lock, and attempting deletion. First get the platform team's expected behavior for data-plane deletes; the work is done when Storage Explorer follows that agreed behavior for locked containers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100