-
Notifications
You must be signed in to change notification settings - Fork 68
Comparing changes
Open a pull request
base repository: puppetlabs/puppetlabs-chocolatey
base: 2.0.2
head repository: puppetlabs/puppetlabs-chocolatey
compare: 3.0.0
- 11 commits
- 13 files changed
- 5 contributors
Commits on May 4, 2017
-
(MODULES-4678) Explicitly close config on read
Previously, any providers managing Chocolatey configuration are unable to be used with 0.10.4+ and actually cause the process to fail. Chocolatey 0.10.4+ has changed the way it updates and accesses the config. The new method has exposed an error in an unclosed file handle when reading the configuration for `chocolateysource`, `chocolateyfeature`, and `chocolateyconfig`. Switch to `File.read` as it will automatically close the file after reading out the contents.
Configuration menu - View commit details
-
Copy full SHA for aed32bf - Browse repository at this point
Copy the full SHA aed32bfView commit details -
Merge pull request #76 from ferventcoder/tickets/master/MODULES-4678_…
…fix_config (MODULES-4678) Explicitly close config on read
Configuration menu - View commit details
-
Copy full SHA for 66b46ac - Browse repository at this point
Copy the full SHA 66b46acView commit details
Commits on May 5, 2017
-
Configuration menu - View commit details
-
Copy full SHA for 0bf3f93 - Browse repository at this point
Copy the full SHA 0bf3f93View commit details -
(MODULES-4562) Use actual choco.exe
Sometimes when running the shimmed choco, it can cause issues and it ends up returning the version of choco as '0'. When managing configuration, this can cause issues using those resources, such as the following: `Failed to apply catalog: Validation of Chocolateysource[chocolatey] failed: Chocolatey version must be '0.9.9.0' to manage configuration values with Puppet. Detected '0' as your version. Please upgrade Chocolatey to use this resource.` On the next run of Puppet, everything works again appropriately. The event log shows an issue with attempting to run the shim. In order to avoid this altogether, just use choco.exe directly when running Puppet.
Configuration menu - View commit details
-
Copy full SHA for 47e2cdf - Browse repository at this point
Copy the full SHA 47e2cdfView commit details -
Merge pull request #77 from ferventcoder/ticket/master/MODULES-4562_u…
…se_original_choco (MODULES-4562) Use actual choco.exe
Configuration menu - View commit details
-
Copy full SHA for 82a205b - Browse repository at this point
Copy the full SHA 82a205bView commit details
Commits on May 11, 2017
-
* release: (MODULES-4633) Prepare for 2.0.2 module release
Configuration menu - View commit details
-
Copy full SHA for 3199f6c - Browse repository at this point
Copy the full SHA 3199f6cView commit details
Commits on May 23, 2017
-
Configuration menu - View commit details
-
Copy full SHA for f4061ca - Browse repository at this point
Copy the full SHA f4061caView commit details -
Configuration menu - View commit details
-
Copy full SHA for 8a2bdad - Browse repository at this point
Copy the full SHA 8a2bdadView commit details -
Merge pull request #78 from chsnell/ticket/MODULES-4846-metadata_update
(MODULES-4846) Update metadata
Configuration menu - View commit details
-
Copy full SHA for b491a88 - Browse repository at this point
Copy the full SHA b491a88View commit details
Commits on May 30, 2017
-
(MODULES-4994) Prepare module for 3.0.0 release
This commit prepares the module for 3.0.0 release.
Configuration menu - View commit details
-
Copy full SHA for f503a81 - Browse repository at this point
Copy the full SHA f503a81View commit details -
Merge pull request #79 from glennsarti/ticket/release/modules-4994-pr…
…ep-3.0.0 (MODULES-4994) Prepare module for 3.0.0 release
Configuration menu - View commit details
-
Copy full SHA for ccf9b89 - Browse repository at this point
Copy the full SHA ccf9b89View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 2.0.2...3.0.0