Open GrimAnEye opened 2 weeks ago
Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey. Please be sure to review our Code of Conduct. Also, check out some of our community resources including:
There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar. If you have additional questions, email us at saltproject@vmware.com. We’re glad you’ve joined our community and look forward to doing awesome things with you!
What does this PR do?
The existing Windows and MS Office license management module is based on supplied vbs-scripts from these products themselves.
Microsoft itself is phasing out vbscript, but what remains is a flexible and functional CIM( 1, 2 ) tool that can be called via Powershell.
My module is an implementation of license key management via CIM methods, universal to all software that uses the Windows internal license store.
What issues does this PR fix or reference?
None, it's a new module
Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.
Commits signed with GPG?
No