-
Notifications
You must be signed in to change notification settings - Fork 94
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
CMR-9848: When submitting multiple associations, if one fails CMR returns a 400 but still makes the other associations #2174
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2174 +/- ##
==========================================
- Coverage 58.15% 58.14% -0.01%
==========================================
Files 1045 1045
Lines 70428 70430 +2
Branches 2001 1998 -3
==========================================
- Hits 40959 40954 -5
- Misses 27610 27612 +2
- Partials 1859 1864 +5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@@ -3857,7 +3857,7 @@ curl -XDELETE -i -H "Content-Type: application/json" -H "Authorization: Bearer X | |||
{"concept_id": "C1200000006-PROV1"}, | |||
{"concept_id": "C1200000007-PROV1"}]' | |||
|
|||
HTTP/1.1 400 Bad Request | |||
HTTP/1.1 400 Bad Request |
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.
HTTP/1.1 400 Bad Request | |
HTTP/1.1 200 Bad Request``` | |
Isn't this example also `200` since the `C1200000005-PROV1` in the example would have succeeded? |
Overview
What is the feature/fix?
Return proper status when processing association requests.
What is the Solution?
When processing association request, only return 400 status when ALL associations fail, rather than when ANY association fails. This includes all generic associations and regular associations, except for tag association. When I changed tag associations return status from 400 to 200 with only partial failure, for some mysterious reason, some ACL related stuff failed in the build, which I really don't see any connection with the fix. I'm writing a separate ticket for the tag association part since I don't have time to fix it.
What areas of the application does this impact?
CMR search.
Checklist