microsoft / microsoft/AzureStorageExplorer
Consider making location of the versioning blobs private
Open
Nobody has claimed this yet.
:test_tube: engineering
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
This will likely require registering some app identifier so Storage Explorer can still access the versioning blobs.
We should also examine the other publicly accessible containers in the same 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
No files, tests, or entry points are identified. Start by locating the versioning-blob configuration and the other publicly accessible containers, then determine how an app identifier would preserve Storage Explorer access; done means the relevant containers are private without breaking that access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100