-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add DRS compact identifier support #20410
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
jmchilton
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very exciting - thanks for the tests!
f6b199f to
298521a
Compare
de0f1f3 to
d40e20f
Compare
|
This one probably needs a rebase to see if the linting errors are gone |
|
I'm going to rebase this and prune it back to what was approved and not try to do drs-via-filesources in this branch, that will be a followup. |
Support compact identifiers (e.g., drs://drs.anv0:object-id) by resolving prefixes via identifiers.org. Includes caching and tests.
Refactor S3 download logic, add type hints, enhance error handling
|
I need to add a test update back to this I think, then we're good to go. |
The access_id resolution logic now prefers fetching from /access/{id}
when present, so tests need to mock that endpoint rather than providing
inline access_url in the object response.
Galaxy's DRS response can include access_id: None, so we need to check for truthy values, not just key existence.
Support compact identifiers (e.g., drs://drs.anv0:object-id) by resolving prefixes via identifiers.org. Includes caching and tests.
How to test the changes?
(Select all options that apply)
License