-
Notifications
You must be signed in to change notification settings - Fork 78
Comparing changes
Open a pull request
base repository: puppetlabs/puppetlabs-powershell
base: 2.1.4
head repository: puppetlabs/puppetlabs-powershell
compare: 2.1.5
- 17 commits
- 7 files changed
- 6 contributors
Commits on Mar 29, 2018
-
Merge pull request #219 from RandomNoun7/release
(MODULES-6937) Mergeback release to master
Configuration menu - View commit details
-
Copy full SHA for 1bcbfcf - Browse repository at this point
Copy the full SHA 1bcbfcfView commit details
Commits on Mar 30, 2018
-
(maint) Remove errant pry command
This commit removes an errant pry command that was commented out. [skip ci]
Configuration menu - View commit details
-
Copy full SHA for da3df5e - Browse repository at this point
Copy the full SHA da3df5eView commit details -
Merge pull request #220 from glennsarti/master
(maint) Remove errant pry command
Configuration menu - View commit details
-
Copy full SHA for 031c37a - Browse repository at this point
Copy the full SHA 031c37aView commit details
Commits on Apr 18, 2018
-
(MODULES-4271) Add Server 2016 to metadata
This commit adds Server 2016 to the list of supported Windows OSes.
Configuration menu - View commit details
-
Copy full SHA for d946415 - Browse repository at this point
Copy the full SHA d946415View commit details -
Merge pull request #221 from glennsarti/add-2016
(MODULES-4271) Add Server 2016 to metadata
Configuration menu - View commit details
-
Copy full SHA for 4f8cd1d - Browse repository at this point
Copy the full SHA 4f8cd1dView commit details -
(MODULES-7011) Fix .NET upgrade message
When using this module with PowerShell 2.0, the only way to use the enhanced commonication method is to have .NET 3.5 installed. The warning message a user received however implied that if you installed any version higher than 3.5, such as .NET 4.0, that the message should go away, and receiving it was a bug in the check logic, which was testing specifically for .NET 3.5 and not >= 3.5. Unfortunately, our testing confirmed that installing .NET 4.0 on a machine is not enough to enable the enhanced features in the module. Having .NET 4 installed does not automatically enable PowerShell 2 to load the newer asseblies or use the more advanced features in that version of the CLR. Specific steps must be taken to enable that to happen, such as editing registry keys, or writing a powershell.exe.config to the disk. The results of doing this are also unpredictable. The change in this commit updates the upgrade message returned to the user to make it clearer that when using PowerShell 2, the only way to enable the enhanced features is to install .NET 3.5, not 3.5+.
Configuration menu - View commit details
-
Copy full SHA for 18628d6 - Browse repository at this point
Copy the full SHA 18628d6View commit details -
Merge pull request #222 from RandomNoun7/tickets/master/MODULES-7011-…
…fix-net-upgrade-message (MODULES-7011) Fix .NET upgrade message
Configuration menu - View commit details
-
Copy full SHA for a7a7b25 - Browse repository at this point
Copy the full SHA a7a7b25View commit details
Commits on Apr 26, 2018
-
(MODULES-7033) Fix Process Kill Test
This change fixes a spec test that was giving unreliable results and erroneously failing CI pipelines.
Configuration menu - View commit details
-
Copy full SHA for 94865de - Browse repository at this point
Copy the full SHA 94865deView commit details -
Merge pull request #223 from RandomNoun7/tickets/master/MODULES-7033-…
…kill-test-unreliable (MODULES-7033) Kill test unreliable
Configuration menu - View commit details
-
Copy full SHA for 5691eb2 - Browse repository at this point
Copy the full SHA 5691eb2View commit details
Commits on May 1, 2018
-
(MODULES-7018) Fix Zero Tmeout Behavior
Some other Puppet Exec providers will treat a `timeout` value of `0` as an infinite timeout. We have chosen not to support an infinite timeout in this provider, so this change will ensure that a sensible value is used if the user passes in `0` as the timeout. It also fixes the README documentation to make it clearer that `0` is not supported, and that attempting to use it will result in the default timeout of 300 seconds being used instead.
Configuration menu - View commit details
-
Copy full SHA for ffc970d - Browse repository at this point
Copy the full SHA ffc970dView commit details
Commits on May 2, 2018
-
Merge pull request #225 from RandomNoun7/tickets/master/MODULES-7018-…
…Fix-timeout-zero-behavior (MODULES-7018) Fix Zero Timeout Behavior
Configuration menu - View commit details
-
Copy full SHA for a97fae9 - Browse repository at this point
Copy the full SHA a97fae9View commit details
Commits on May 3, 2018
-
Configuration menu - View commit details
-
Copy full SHA for 45511a6 - Browse repository at this point
Copy the full SHA 45511a6View commit details -
Merge pull request #226 from RandomNoun7/maint/master/convert-changel…
…og-to-kac (MAINT) Update Changelog to KAC Format
Configuration menu - View commit details
-
Copy full SHA for aca8774 - Browse repository at this point
Copy the full SHA aca8774View commit details -
Configuration menu - View commit details
-
Copy full SHA for e53e96f - Browse repository at this point
Copy the full SHA e53e96fView commit details
Commits on May 4, 2018
-
Merge pull request #227 from RandomNoun7/tickets/release/MODULES-7109…
…-release-prep (MODULES-7109) Release Prep
Configuration menu - View commit details
-
Copy full SHA for b8db498 - Browse repository at this point
Copy the full SHA b8db498View commit details
Commits on May 8, 2018
-
(MODULES-7109) Changelog edits to match KAC format
This commit edited the changelog to follow KAC standards
Configuration menu - View commit details
-
Copy full SHA for 406f38c - Browse repository at this point
Copy the full SHA 406f38cView commit details -
Merge pull request #228 from clairecadman/changelog_edits
(MODULES-7109) CHANGELOG edits
Configuration menu - View commit details
-
Copy full SHA for 610e9e8 - Browse repository at this point
Copy the full SHA 610e9e8View 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.1.4...2.1.5