FEATURE REQUEST - Labconfig - Deployment option to include license key
Open
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1.3k
- Forks
- 304
- PR merge metrics
- No merged PRs in 30d
Description
It would be cool if we could specify a key per VM in Labconfig such as AVMA so we do not have to manually inject and activate.
This should be possible via dism command into the image.
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 locating how Labconfig defines per-VM deployment settings and where the deployment scripts prepare or modify the image. Review the DISM command path for image changes and determine how a per-VM license key would be passed through; done means the configured key is applied during deployment without manual injection or activation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100