-
Notifications
You must be signed in to change notification settings - Fork 47
feat(ga4gh): move DRS access API to fence #957
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
The style in this PR agrees with This formatting comment was generated automatically by a script in uc-cdis/wool. |
Pull Request Test Coverage Report for Build 11677
💛 - Coveralls |
I guess it doesnt matter if we remove this access endpoint from indexd now or later since it would route to fence but we should definitely remove it at some point so as to not bloat indexd. Also should probably add these to the swagger doc |
Yeah, I didn't want to remove it from indexd the same time I added to fence; I want to leave a transition period. It won't necessarily hurt to have the indexd one (people will just get better performance from the fence one). But agreed we should remove it eventually |
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.
LGTM!
Move the /access portion of the DRS API to fence (from indexd). This more closely consolidates the functionality of creating signed URLs into a single service (fence). This should improve performance (as the existing setup requires roundtrip requests from indexd -> fence -> indexd (creating some strange circular dependencies).
New Features
/ga4gh/drs/v1/objects/{object_id}/access/{access_id}
GA4GH DRS Access API via FenceBreaking Changes
Bug Fixes
Improvements
Dependency updates
Deployment changes