forked from chocolatey-archive/puppet-chocolatey
-
Notifications
You must be signed in to change notification settings - Fork 66
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
choco update is deprecated #283
Labels
Comments
chelnak
added a commit
that referenced
this issue
Apr 7, 2022
In situations where the resource described in the manifest includes a version in it's ensure property and choco v1 or above is installed, puppet runs would fail. This was happening of an issue where the version of chocolatey was not being properly derrived by choco_version. In turn, would cause compiled_choco to return false causing the module to default to using choco update rather than choco upgrade. This commit fixes that by ensuring that the choco_version method returns the correct puppet version.
chelnak
added a commit
that referenced
this issue
Apr 7, 2022
In situations where the resource described in the manifest includes a version in its ensure property and choco v1 or above is installed, puppet runs would fail. This was happening of an issue where the version of chocolatey was not being properly derived by choco_version. In turn, would cause compiled_choco to return false causing the module to default to using choco update rather than choco upgrade. This commit fixes that by ensuring that the choco_version method returns the correct puppet version.
chelnak
added a commit
that referenced
this issue
Apr 8, 2022
In situations where the resource described in the manifest includes a version in its ensure property and choco v1 or above is installed, puppet runs would fail. This was happening of an issue where the version of chocolatey was not being properly derived by choco_version. In turn, would cause compiled_choco to return false causing the module to default to using choco update rather than choco upgrade. This commit fixes that by ensuring that the choco_version method returns the correct puppet version.
chelnak
added a commit
that referenced
this issue
Apr 8, 2022
In situations where the resource described in the manifest includes a version in its ensure property and choco v1 or above is installed, puppet runs would fail. This was happening of an issue where the version of chocolatey was not being properly derived by choco_version. In turn, would cause compiled_choco to return false causing the module to default to using choco update rather than choco upgrade. This commit fixes that by ensuring that the choco_version method returns the correct puppet version.
david22swan
added a commit
that referenced
this issue
Apr 8, 2022
…ated (GH-283) Fix deprecation error
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
Chocolatey provider issues deprecation warning for update command:
Expected Behavior
A clear and concise description of what you expected to happen.
Steps to Reproduce
Steps to reproduce the behavior:
Run
choco update
Environment
Module Version: 6.0.1
Puppet Version: 8.26.0
OS Name/Version: Windows
Chocolatey v0.12.1 Business
Additional Context
Running Chocolatey V 1.0.0+ you get the following error if trying to run an update:
The text was updated successfully, but these errors were encountered: