Repository navigation
PD-202 improve metadata functions - #317
Conversation
|
The style in this PR agrees with This formatting comment was generated automatically by a script in uc-cdis/wool. |
Integration TestsTest summary after running integration tests
Test summary after rerunning failed integration tests
Please find the detailed integration test report here Please find the detailed integration test report after rerunning failed tests here Please find the Github Action logs here |
Failure AnalysisPlease find the detailed test analysis report here |
Integration TestsTest summary after running integration tests
Test summary after rerunning failed integration tests
Please find the detailed integration test report here Please find the detailed integration test report after rerunning failed tests here Please find the Github Action logs here |
| return_full_metadata=False, | ||
| limit=10, | ||
| offset=0, | ||
| use_agg_mds=False, |
There was a problem hiding this comment.
what will happen for calls like this that still have use_agg_mds?
gen3sdk-python/gen3/tools/metadata/discovery.py
Lines 164 to 169 in fd1ad6f
use_agg_mds will go into **kwargs and then append_query_params() will add to the request url, and I think breaks
There was a problem hiding this comment.
good catch, i removed this parameter since it is not used
| @@ -588,12 +654,14 @@ def delete_alias(self, guid, alias, **kwargs): | |||
| return response.json() | |||
There was a problem hiding this comment.
MDS DELETE /metadata/{guid}/aliases/{alias} returns 204 (with no json response body allowed), so response.json() errors. The removed version of delete_alias() returned response.text. I think _mock_delete_request in test_metadata.py needs to be fixed to catch this
There was a problem hiding this comment.
per MDS source:
https://github.com/uc-cdis/metadata-service/blob/eefaef4cd18ca3908684d7d5fd8ec6adae3db7f1/src/mds/aliases.py#L115-L121
So this should be 204..
which actually contradicts the API spec which says it returns 200 on successful delete alias!
https://github.com/uc-cdis/metadata-service/blob/eefaef4cd18ca3908684d7d5fd8ec6adae3db7f1/docs/openapi.yaml#L768
There was a problem hiding this comment.
good catch, i updated gen3sdk code and opened this PR to update MDS openapi doc
Integration TestsTest summary after running integration tests
Test summary after rerunning failed integration tests
Please find the detailed integration test report here Please find the detailed integration test report after rerunning failed tests here Please find the Github Action logs here |
Integration TestsTest summary after running integration tests
Test summary after rerunning failed integration tests
Please find the detailed integration test report here Please find the detailed integration test report after rerunning failed tests here Please find the Github Action logs here |
Failure AnalysisPlease find the detailed test analysis report here |
Integration TestsTest summary after running integration tests
Test summary after rerunning failed integration tests
Please find the detailed integration test report here Please find the detailed integration test report after rerunning failed tests here Please find the Github Action logs here |
Link to JIRA ticket if there is one: https://ctds-planx.atlassian.net/browse/PD-202
New Features
Breaking Changes
Bug Fixes
Improvements
gen3.metadata.Gen3Metadata.query()no longer requires aqueryparameter, if omitted, all metadata record with MDS will be returned (subject tolimitandoffset)gen3.metadata.Gen3Metadata()no longer requires agen3.auth.Gen3Authobject during initialization. If functions that requires auth will be called, an message will be posted to the user and the call will return directlyDependency updates
Deployment changes