-
Notifications
You must be signed in to change notification settings - Fork 3
feat: process-ecr api endpoint
#712
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #712 +/- ##
==========================================
+ Coverage 87.55% 91.09% +3.53%
==========================================
Files 274 140 -134
Lines 14215 5311 -8904
Branches 903 915 +12
==========================================
- Hits 12446 4838 -7608
+ Misses 1752 456 -1296
Partials 17 17
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…gov/dibbs-ecr-viewer into mcm/feat-api-process-message
process-message api endpoint
process-message api endpointprocess-ecr api endpoint
…o mcm/feat-api-process-message
JNygaard-Skylight
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.
LGTM!
PULL REQUEST
Summary
Add the
process-ecrendpoint to the viewer. Similar to theprocess-zipendpoint for the viewer, hardcode the fields that are known and only ask for the data. The message endpoint supports both form and json data (because Rhapsody 6 can't do forms in a sane way 😭 ).Rewrite
process-ziprequests intoprocess-ecrvia middleware and have the logic for getting the data and putting it in the right place over onprocess-ecr. Left a readme to that effect in the api folder so that lost souls might find their way.Related Issue
Fixes #698
Acceptance Criteria
New /process-message endpoint exists on eCR Viewer
New endpoint should:
Accept eICR and RR in the request body, like orchestration does today
Determine which orchestration configuration is applicable based on eCR Viewer environment variables (AWS, Azure, integrated, non-integrated, etc)
Send the eCR and RR to the orchestration service for processing
Accept the orchestration response
Save eCR data from orchestration (to S3, SQL Server, etc)