MHR API - Build new service agreement endpoints

[mstanton1]

Create the following terms of agreement (terms) endpoints

• GET /mhr/api/v1/service-agreements Get a list of all available service agreement versions (may not be used by the UI).
• GET /mhr/api/v1/service-agreement/{termsVersion} to retrieve a specific version of the service agreement document either as JSON summary info or as a PDF. Use request header Accept=application/pdf to request the PDF data as a response.
• POST /mhr/api/v1/service-agreement/{termsVersion} Accept the service agreement terms at the user level when the user is required to re-accept.

Note: the API endpoints to submit the account qualified supplier/manufacturer information will not automatically record the current version of the service agreement terms at the time of submission as accepted. These endpoints are:

• POST /mhr/api/v1/qualifed-suppliers
• POST /mhr/api/v1/manufacturers Either explicitly set termsAccepted=true in the above Post requests or use the POST /mhr/api/v1/service-agreement/{termsVersion} to set the acceptance of the agreement after the information has been stored.

Tasks

• [x] Create new GCP cloud storage bucket and manually upload the initial version of the document.
• [x] Create db tables to track account/user acceptance and to reference versions of the document.
• [x] Update the MHR API spec.
• [x] Update the MHR qualifiedSupplier and manufacturer schemas. Add the termsSummary schema.
• [x] Build the API endpoints and unit tests.

[doug-lovett]

UI only so perhaps test with UI?

Unit testing in DEV: Get list of agreements: GET https://bcregistry-dev.apigee.net/mhr/api/v1/service-agreements

Get agreement PDF: Request header Accept=application/pdf GET https://bcregistry-dev.apigee.net/mhr/api/v1/service-agreements/latest

Accept agreement: POST https://bcregistry-dev.apigee.net/mhr/api/v1/service-agreements/latest { "agreementType": "DEFAULT", "version": "latest", "accepted": true }

[chdivyareddy]

Verified in TEST!

Private Zenhub Image