microsoft / microsoft/AzureTRE
Workspace User and Shared Storage
Open
Nobody has claimed this yet.
feature
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
-
#1566
-
#1266
-
#1267
Notes
- User storage does not need to be private, but dedicated to the user. Private per user storage may come later.
- Drives should be mounted into relevant locations - the mounting is a function of the user resource template - it may be different for different user resources.
- Creation of shared storage will be a function of the base workspace template
- Creation of user storage - TBD - but possible when a user resource is deployed to create if does not exist
- User shares should be created per user, with a unique identifiers - such as Azure AD object ID.
Contributor guide
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 reviewing linked issues #1566, #1266, and #1267, then examine the workspace and user resource templates that define storage and drive mounting. Clarify the creation and per-user sharing requirements before implementation; done should cover shared workspace storage, user-dedicated storage, and unique per-user shares.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100