-
Notifications
You must be signed in to change notification settings - Fork 4
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
AJ-1496: remove /api/duos/consent/orsp/{orspId} API #1249
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #1249 +/- ##
===========================================
- Coverage 69.94% 69.36% -0.59%
===========================================
Files 101 97 -4
Lines 3500 3401 -99
Branches 371 381 +10
===========================================
- Hits 2448 2359 -89
+ Misses 1052 1042 -10 ☔ View full report in Codecov by Sentry. |
} | ||
Future.successful(annotatedWorkspaces map { w => indexableDocument(w, parentMap, ontologyDAO) }) |
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.
changes in this class are the only real functional changes. Previously, we called consentDAO.getRestriction(orspId)
if an ORSP id was present, and the remainder of the code was dedicated to handling the responses. Now, since that call will never succeed, the code is much simplified.
martha didn't start in automation tests. Jenkins retest. |
martha didn't start again. Is this a persistent problem? Jenkins retest. |
Jenkins retest. |
Jenkins retest |
Delightful red diff. B-B-B-Bonus multiplier 💰 💰 💰 💰 for deleting Scala. (sorry Scala) |
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.
Sorry I meant to approve this first time around and just left an cheerleading comment instead! Rectified.
The Consent service has removed the ability to look up an ORSP id and return the data use restrictions for that ORSP id. The API that Orch used to call for this now returns a 404 all the time.
Thus, this PR removes the call from Orch to Consent for this lookup, and removes Orch's own
/api/duos/consent/orsp/{orspId}
API. Technically, removing this API would be a breaking change. However, since Consent will always return a 404, if Orch kept its API alive it would also always return a 404. Instead, let's remove the API entirely … which will also return a 404.By removing the call from Orch to Consent for this lookup, Orch can subsequently delete a whole bunch of code and unit tests. In fact, Orch can even remove Consent as a subsystem from its
/status
API.Once this merges and is stable, I will follow up sometime after with a PR to remove the consent url from Orch's config: https://github.com/broadinstitute/terra-helmfile/blob/0935fb0a1fd3494fd2d7bfc09f4ada55c981fa27/charts/firecloudorch/templates/config/_conf.tpl#L344
Have you read CONTRIBUTING.md lately? If not, do that first.
I, the developer opening this PR, do solemnly pinky swear that:
In all cases: