(docs) update filebucket doc to reflect cryptographic checksum instead of md5 #9117
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
|
|
…d of md5 specifically
golflimaechoecho
force-pushed
the
update_filebucket_doc_comment
branch
from
186b38f to
6f5e338
Compare
joshcooper
approved these changes
Oct 5, 2023
|
Successfully created backport PR for |
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.
Default digest_algorithm changed in Puppet 7.0.0; update filebucket documentation to reflect no longer md5 by default.
The algorithm used is specified by the digest_algorithm setting; md5 was the default for Puppet6 and earlier; from Puppet 7.0.0 onwards the default was changed to sha256 - ref: https://www.puppet.com/docs/puppet/7/release_notes_puppet.html#enhancements_puppet_7-0-0-pup-10583