microsoft / microsoft/devcenter-catalog
Implement 'RunAsUser' feature in powershell task
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 52
- Forks
- 194
- Avg merge
- 16h 53m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
Some setup tasks need to run in user logon session like Show dialog and accept license agreement, Mount SMB file share as drive, Install vscode extension, etc..
So I think RunAsUser feature is important and should be provided by powershell task cataloged in this repo.
It seems curious that git-clone and winget task have implementation while powershell task doesn't have.
Describe the solution you'd like
Like powershell task in advanced samples repo.
But it has mistake in task.yaml, not 'defaultValue' but 'default' for default value.
Describe alternatives you've considered
I think this 'RunAsUser' feature is universal, so it should be provided by CaC feature of DevBox itself, not by each tasks.
Additional context
I think the quick start catalog is very important for developer team.
I'm looking forward to expanding the capabilities.
Thanks !
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 comparing the existing git-clone and winget task implementations with the powershell task, then review the advanced-examples customization-wsl/task.yaml linked in the issue. Confirm the expected RunAsUser behavior and the corrected default field, and consider whether the feature belongs in the task or DevBox itself. Done means the powershell task supports the agreed behavior and its catalog definition is valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100