microsoft / microsoft/DurableFunctionsMonitor
Permissions for identities clarification
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 290
- Forks
- 46
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
Would be nice to document what the least permissions required are, in order to get the VSCode extension running, when connecting via identity to a storage account (task hub) in Aure.
I've discovered that it needs at least the following to display information and not throw an error:
- Storage Blob Data Reader
- Storage Table Data Reader
Ideally, it shouldn't need Storage Blob Data Reader unless there is a <taskhub>-largemessages container as specified here, even then it shouldn't really be required, right? Or is there more to the blob part? Would love to see that dependency gone. By the way, reading out containers is not a dataAction so that can be a simple Reader-role if you're going to check on that.
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 tracing the VSCode extension's identity-based access to the Azure storage account and task hub, then compare the observed requirements with the Azure storage provider documentation linked in the issue. Document the minimum roles needed to display information and clarify whether Storage Blob Data Reader is required for large-message containers or can be removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- authorization, cloud
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100