chocolatey / chocolatey/ChocoCCM
Add a more accurate chocolatey license check
- Dominant language
- PowerShell
- Stars
- 7
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
## Is Your Feature Request Related To A Problem? Please describe.
In b9b3ec3b40d454a18aa851bf3bad61ed2b05bb60 we removed a check for a Chocolatey license, because the check was simply looking for _any_ file at the appropriate path, not validating the license at all, and causing complications in getting the build servers up and running.
## Describe The Solution. Why is it needed?
Possibly look for and import the Chocolatey / licensed assemblies and do a proper license check assertion? We can do better here, at least, in some way.
Note that we will also need to ensure we license any build agents building this module if we choose to restore the check.
## Additional Context.
See #70
## Related Issues
N/A
Contributor guide
No contributing guide indexed for this repository
Research direction
Review commit b9b3ec3b40d454a18aa851bf3bad61ed2b05bb60 and issue #70 to understand the removed Chocolatey license check and its build-server impact. Determine which licensed assemblies and validation behavior are appropriate, and document how build agents would be licensed before defining what a successful check means.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100