Fix links to the new SHA512 checksums and check the integrity directly #27524
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
|
Please also cherry-pick to the 6.x branch. |
mgreau
approved these changes
Nov 29, 2017
jasontedor
pushed a commit
that referenced
this pull request
Nov 30, 2017
This commit updates the docs for the new SHA-512 checksums that are supported for official plugins. Relates #27524
jasontedor
pushed a commit
that referenced
this pull request
Nov 30, 2017
This commit updates the docs for the new SHA-512 checksums that are supported for official plugins. Relates #27524
jasontedor
pushed a commit
that referenced
this pull request
Nov 30, 2017
This commit updates the docs for the new SHA-512 checksums that are supported for official plugins. Relates #27524
|
Thanks for merging, @jasontedor — I got too busy with community work the last few days... |
|
No worries @xeraa, thank you for the PR. |
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.
We don't provide SHA1 any more for 6.0+ artefacts, so the link is currently broken. Also switched to checking the integrity directly instead of comparing hashes.
Related blog post: https://www.elastic.co/blog/sha512-checksums-for-elastic-stack-artifacts ( @mgreau )
Will cherrypick to 6.0 and 6.1 branches if approved.