PDF Generator - Demo Endpoint + Redis

[anthonyvelazquez]

PDF Generator - Demo Endpoint + Redis

Description

What was the problem?

Incorrect API endpoint for the PDF generator

How does this fix it?

Update the previous demo endpoint to use the new fields based on #113. Added Redis instead of using S3 to store the PDF file and split the functionality into 2 endpoints, a generate and a fetch request.

How to test this PR

More details in README.md

Request Body:

    {
    "claimSubmissionId": "1",
    "diagnosticCode": "7701",
    "veteranInfo": "{\"first\": \"test\",\"middle\": \"test\", \"last\": \"test\", \"suffix\": \"test\", \"birthdate\": \"2000-10-20\"}",
    "evidence": "{\"bp_readings\":[], \"medications\":[]}"
  }

You can fill evidence with additional information as long as it matches the format in Assess Claims here: #113

• Send a request with the request body to: http://localhost:8080/v1/demo/generate_pdf
• Send a request with the request body to: http://localhost:8080/v1/demo/fetch_pdf
• NOTE: If you use Postman to try these endpoints, the PDF will display in the response window

[jbregstone]

This is great! I tested it with postman with some sample data and it worked perfectly. On possible improvement would be to change the fetch_pdf endpoint to only require the "claimSubmissionId" field because it does not need the "evidence" to return the right pdf, but that is not absolutely necessary so I will approve.

[yoomlam]

Let's remove/rename the demo package once you've finalized the new endpoints. The demo package is meant to be temporary.

[yoomlam]

Since you've modified it to be used for the new endpoints that will be called by RRD, this DemoController class should be removed/renamed and put in a different Java package.