Require Agreement Names to be unique (Backend Validation)
Description
is defined by
Checklist
hideTestRail: Results
Activity
Show:
Owen Stephens May 21, 2020 at 2:23 PM
@Ethan Freestone Looking at this, I think the paths are:
/erm/validate/subscriptionAgreement
/erm/validate/subscriptionAgreement/name
rather than the ones given here?
Done
Details
Details
Components
Assignee
steve.osguthorpe
steve.osguthorpeReporter
Ethan Freestone
Ethan FreestoneLabels
Priority
Sprint
None
Development Team
Bienenvolk
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created May 18, 2020 at 8:37 AM
Updated June 1, 2020 at 10:22 AM
Resolved June 1, 2020 at 10:22 AM
TestRail: Cases
TestRail: Runs
Agreement names should be validated for uniqueness in back end.
New controller for endpoint `erm/sas/validate`
curl -H 'X-OKAPI-TENANT: diku' -H 'Content-Type: application/json' http://localhost:8080/erm/sas/validate -XPOST -d '{ "name": "Test" }' | jq
attempts to validate sent object as entire agreement, so use
curl -H 'X-OKAPI-TENANT: diku' -H 'Content-Type: application/json' http://localhost:8080/erm/sas/validate/name -XPOST -d '{ "name": "Test" }' | jq
to just validate the name "Test".