Capability statement

[elsaperelli]

Summary

Adds a /metdata endpoint to the server to display the capability statement. This is mostly so our server does not show a 404 error in ConMan for the Connectathon!

New behavior

/metadata endpoint returns a 200 code and the capability statement JSON found here. I believe it is reflective of our server's capabilities, but not sure if I need to remove or add anything.

Code changes

• src/config/capabilityStatementResource.json - capability statement grabbed from the Bulk Data Access IG
• src/server/app.js - add /metadata endpoint
• metadata.service.js - service for the capability statement /metadata endpoint

Testing guidance

• Make sure this makes sense as a capability statement.
• npm start
• Send a GET request through Insomnia (or whatever) to http://localhost:3000/metadata and make sure a 200 status code is returned as well as the capability statement.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	79.36% (-0.23% 🔻)	473/596
🟡	Branches	66.53%	167/251
🟡	Functions	77.08% (-0.81% 🔻)	74/96
🟡	Lines	79.79% (-0.24% 🔻)	466/584

Show new covered files 🐣

St.❔	File	Statements	Branches	Functions	Lines
🔴	... / metadata.service.js	50%	100%	0%	50%

Test suite run success

76 tests passing in 7 suites.

Report generated by 🧪jest coverage report action from 0379016