surfacing package_ensure in README #181
Merged
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
Dan33l
force-pushed
the
package_ensure_datatype
branch
from
97029ba to
dfc2c04
Compare
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.
Pull Request (PR) description
The default install method is to use package from distribution.
Let's Encrypt, as released in Xenial, stopped to work since 13 March 2019 when TLS-SNI-01 validation is turned off by the primary Let's Encrypt CA. This makes the package effectively useless for just about all users.
Ubuntu 16.04 maintainers upgraded the package from 0.4 to 0.7, and so it is necessary to upgrade the package to the new version. The default
ensure => installedattribute forpackageresource does nothing.So it looks interesting to explain how to upgrade the package with the puppet module.
This Pull Request (PR) fixes the following issues