Skip to content
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

powershell_package resource does not use 'options' property #9129

kimbernator opened this issue Dec 2, 2019 · 0 comments


Copy link

@kimbernator kimbernator commented Dec 2, 2019


powershell_package documentation advertises that it can use the options property to append an arbitrary array of strings (or one string) to the end of the installation command to allow flexibility. This comes from the parent package resource/provider and appears to work for all other children of package (e.g. rpm, pacman, etc.) because they specifically make use of it. powershell_package does not reference options at all while forming its commands (link to file)

Chef Version


Platform Version

Windows Server 2012R2

Replication Case

  1. Install a powershell module that is older than the newest available version:
install-package '<your module name>' -requiredversion <version>
  1. Run the following resource:
powershell_package `<your module name>` do
  action :install
  options '-InstallUpdate'
  1. Check installed powershell modules and see that the newest version is not installed
get-package '<your module name>' -allversions

Client Output




Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.