Merge master to next #484
Merged
Merge master to next #484
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Remove travis badge
fix hiera example in documentation
the apt module did not correctly detect Cumulus Linux with lsbdistid. This change adds several lines in params.pp to detect Cumulus Linux and set $distid and $distcodename
…mulus-linux MODULES-1827 adding Cumulus Linux detection
better attempt at gpg version checking adding in key length warning removing version check, adding key check adding tests clean up the code small changes use commands documentation updates
This is cherry-picked from the PPA cleanup happening for the 2.0.0 release. Conflicts: manifests/params.pp manifests/ppa.pp
…erties Make installation of software-properties optional
…unattended-upgrades Cleaning 50unattended-upgrades.erb
…_version initial commit for apt_key checking
This enables using Origins-Pattern in Ubuntu.
Allow changing legacy_origin
Update docs for unattended_upgrades
If one should happen to have redirected /usr/bin/gpg to run GnuPG 2.x rather than the more usual GnuPG 1.x, the apt_key provider fails with the following error: Could not prefetch apt_key provider 'apt_key': invalid date This is because the output of "--with-colons" defaults to using "fixed-list-mode" in 2.x but did not do so for 1.x. This new format gives much more information about keys and also uses timestamps in seconds from 1970-01-01 (UNIX epoch) rather than dates in the format YYYY-MM-DD. This patch adds "--fixed-list-mode" when calling apt-key, and adjusts the code to parse the timestamps instead. This actually has several advantages: - Works the same with GnuPG 1.x and 2.x. - More accurate expiry time tracking, not just entire days. - No need to require 'date' any longer. - Will allow the provider to expose more key information in future. Tested on: - Debian Wheezy (Puppet 2.7.23, Ruby 1.8.7p358) - Debian Jessie (Puppet 3.7.2, Ruby 2.1.5p273)
apt_key: fix parsing invalid dates when using GnuPG 2.x
Use the full fingerprint for all keys to silence the warning.
Fix gpg key checking warings after f588f26
Merged puppetlabs#466 too quickly
Update all the unit tests to look for full fingerprints
Merge 1.8.x to master
documented more common parameters
…tended-upgrades Extend docs for unattended_upgrades
puppetdb, etc - support for BEAKER_VERSION and BEAKER_RSPEC_VERSION in gemfile
(BKR-147) add Gemfile setting for BEAKER_VERSION for puppet...
Updated key fingerprints in README to match v1.8.0 requirements
|
intentionally did a merge instead of a rebase to make the history a little less terrible. |
|
This should wait until #483 is merged. |
|
Or actually... doesn't really matter. It's master to next, not next to master, derp. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
it's about that time 😺