Add support for custom md5 remote path. #49
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
shk3
reviewed
Jun 20, 2024
Make clear a md5 hash is needed for http-checksum-url.
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 use the gitlab package registry to store ansible playbook releases. Gitlab has permalinks to the latest artifacts or to release assets. These links to artifacts or release assets are accessed using the gitlab API and my not be the actual path to the tarball or md5 checksum file.
A custom remote path for the link to the md5 hash would be very nice! This PR will add a
http-checksum-urlflag. If thehttp-checksum-urlflag has not been set, it will use thehttp-urlwith.md5added to the path.