Replies: 1 comment 1 reply
-
UPDATE: My original files were uploaded using a makeshift PowerShell script. But after using |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I came across this library today and found it to be very helpful! However, I encountered one minor issue while using it and wanted to mention it here to see if it made sense to request a change or start a pull request:
When calling
artifact_info = art.artifacts.info(ARTIFACT_PATH)
, I receive the following Pydantic validation error:When looking into this error message, I inspected the
response.json()
and noticed that originalChecksums did not have asha1
field:{... 'originalChecksums': {'md5': 'ef4bdeccdbdf8af2d0da9170b8e491f4', 'sha256': '704b68b397edc2a2ba2a3f7704e07f5ff7a3707c0f024eaf8ca5061c0bedb43d'} ...}
As a workaround I modified the OriginalChecksums model from...
...to...
...and was able to finish my writing a script to download an artifact and verify it's MD5 checksum. However, for future uses it would be nice to not have to implement this monkey patch, hence, thought I'd bring it up for discussion to see if it made sense to request this change.
I tried searching Artifactory REST API to see I could find any additional informational info about the
originalChecksums
object and its fields to see if the documentation called it out as an optional field, but didn't find anything to address this question. However, I did find this note on StackOverflow:Perhaps this user error on my part by not uploading the file correctly in the first place?! I'm new Artifactory user and eager to learn from others.
Thanks,
Chris
Beta Was this translation helpful? Give feedback.
All reactions