Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
eHoldings Sprint 86, eHoldings Sprint 90, eHoldings Sprint 91
-
3
-
Spitfire
Description
Support partial update of KB credentials by following endpoint:
PATCH /eholdings/kb-credentials/{credentialsId}
Request body might contain all credentials attributes, but at least one is required. The attributes that are absent should be taken from old version of credentials. For instance the following request can be used to replace credentials' name only:
{"data": { "id":"1879626b-1e99-4449-ab91-9fc620bb78ad", "type":"kbCredentials", "attributes":{ "name":"Knowledge base" }, "meta":{ "createdDate":"2020-06-02T07:13:47.501+0000", "createdByUserId":"2e5b4486-ec72-502f-8dc0-7608636cd096", "createdByUsername":"user1" } } }
Requirements
- KB credentials entity information can be partially updated
- an error is returned if KB API Credentials are invalid
Acceptance Criteria
- the endpoint created and works according to the requirements
- the endpoint is covered with unit tests
- API tests created to cover endpoint functionality
TestRail: Results
Attachments
Issue Links
- is defined by
-
MODKBEKBJ-390 Spike: describe design for "Single tenant multiple EBSCO KBs" scenario
-
- Closed
-
- is required by
-
UIEH-898 Unable to change KB Name value
-
- Closed
-
- relates to
-
MODKBEKBJ-393 Spike "Single tenant + KBs": Managing KB Credentials in MOD KB EBSCO module
-
- Closed
-
-
RMB-688 PATCH to update only some JSONB properties
-
- Open
-
-
UXPROD-2463 Q3 2020 | Multiple KBs in a single tenant
-
- Closed
-