-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
win_chocolatey does not support licensed edition options/switches #15
Comments
Up until recently, these modules were part of Ansible's core modules, so while I can't speak for them I would guess that they felt it was better to have the modules mainly support open source Chocolatey features. We can look at adding some of the licensed edition features if there's a need for it, absolutely. There are some things we'd need to iron out on our end, mainly to do with how we'd handle testing for those features (after all, can't really test those things without a valid Chocolatey license on the Windows agent). I'm more than happy to take a look at what's missing and add some of the licensed features in as my work schedule permits. If you or anyone else would like to submit PRs for specific features that you have a pressing need for, that's more than welcome as well. 🙂 |
This came up in today's webinar. Something we should definitely look into fixing for the next version of this. |
So Chocolatey will typically ignore most arguments if it doesn't understand them, that's the default. There is one ( I would suggest an option called |
Worth noting that we already have:
I think it would be best if we made the new option a bit more distinct than just Perhaps something like |
This allows users to specify arguments that are not explicity supported by the collection, for example any options that require the chocolatey licensed extension to be installed. This also gives us a workaround / stop-gap for any additional arguments in open source Chocolatey in future, allowing users to specify them manually until the collection is updated to include those options.
This allows users to specify arguments that are not explicity supported by the collection, for example any options that require the chocolatey licensed extension to be installed. This also gives us a workaround / stop-gap for any additional arguments in open source Chocolatey in future, allowing users to specify them manually until the collection is updated to include those options.
This allows users to specify arguments that are not explicity supported by the collection, for example any options that require the chocolatey licensed extension to be installed. This also gives us a workaround / stop-gap for any additional arguments in open source Chocolatey in future, allowing users to specify them manually until the collection is updated to include those options.
This allows users to specify arguments that are not explicity supported by the collection, for example any options that require the chocolatey licensed extension to be installed. This also gives us a workaround / stop-gap for any additional arguments in open source Chocolatey in future, allowing users to specify them manually until the collection is updated to include those options.
This allows users to specify arguments that are not explicity supported by the collection, for example any options that require the chocolatey licensed extension to be installed. This also gives us a workaround / stop-gap for any additional arguments in open source Chocolatey in future, allowing users to specify them manually until the collection is updated to include those options.
This allows users to specify arguments that are not explicity supported by the collection, for example any options that require the chocolatey licensed extension to be installed. This also gives us a workaround / stop-gap for any additional arguments in open source Chocolatey in future, allowing users to specify them manually until the collection is updated to include those options.
(#15) Allow additional choco args to be passed manually
When attempting to install the chocolatey-management-database|service|web packages, I noticed that there was no means of passing a value to the choco --package-parameters-sensitive option. I then also noticed that the other options avaialable to licensed users are also missing.
Is this an oversight, or intentional?
The text was updated successfully, but these errors were encountered: