[FOLIO-2617] Request to Update ebsco-rmapi-config settings for Hosted Reference Environments Created: 28/May/20  Updated: 22/Jun/20  Resolved: 22/Jun/20

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Story Priority: P2
Reporter: Carole Godfrey Assignee: David Crossley
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Screen Shot 2020-06-10 at 10.55.33 PM.png    
Issue links:
Blocks
is blocked by FOLIO-2632 Request to configure diku_admin user ... Closed
Relates
relates to FOLIO-2652 Refine ebsco-rmapi-config settings fo... Closed
Sprint: DevOps: sprint 90
Development Team: FOLIO DevOps

 Description   

The location where eHoldings application stores its configuration for rm api credentials is changing in Q2-2020.

These changes have been merged into master branch
https://github.com/folio-org/mod-kb-ebsco-java/pull/272/files

Without configuration changes, hosted reference environments which are built from master will not have kb credentials configured for the eHoldings application

Prior to this change - configuration for rm api credentials are gotten from mod-configuration (believe this is the reference in ansible project)

https://github.com/folio-org/folio-ansible/blob/7c629b8d1fdee85dbafe64b03adca06103f612f8/roles/ebsco-rmapi-config/tasks/main.yml

We'd like request that the 3 configuration api calls be replaced with a single POST request to a new /eholdings/kb-credentials endpoint
(substituting in appropriate values for rmapi_custid, rmapi_key, rmapi_url) – note that this endpoint is new – older reference environments such as fameflower will continue to need to be configured using 3 mod-configuration values

POST /eholdings/kb-credentials
{
 "data": {
  "type": "kbCredentials",
  "attributes": {
   "name": "OpenTown Libraries",
   "apiKey": "XXXX",
   "url": "YYYY",
   "customerId": "ZZZZ"
  }
 }
}


 Comments   
Comment by David Crossley [ 11/Jun/20 ]

Carole Godfrey The configuration is done and tested with Jenkins build folio-snapshot-test #158

The nightly builds of reference environments will utilise this on their next run.

Comment by Carole Godfrey [ 11/Jun/20 ]

Thank you David Crossley

Comment by David Crossley [ 11/Jun/20 ]

I needed to temporarily disable the "ebsco-rmapi-config" for the Jenkins "folio-release" build.

Its ansible playbook also uses the master of folio-ansible (as does snapshot and testing), hence fails because the module is not yet released with that new endpoint.

Comment by David Crossley [ 11/Jun/20 ]

Today's "folio-snapshot" Jenkins builds are okay.

Comment by Carole Godfrey [ 11/Jun/20 ]

The latest code in master uses a newer endpoint for those credentials. Older reference environments would not have this newer endpoint available from the API
https://folio-snapshot-test.aws.indexdata.com/settings/eholdings/knowledge-base/3225c0d4-c38d-41f9-9dec-3754c06460fc

Older environments would continue to need to be configured using the 3 configuration endpoints

Also David Crossley we would like the name to say either "OpenTown Libraries" or "Knowledge Base" instead of the tenant diku (it seems to be showing tenant id instead of a tenant display name) - could this be updated?

Comment by David Crossley [ 15/Jun/20 ]

The name "OpenTown Libraries" is set by the front-end Stripes configuration. So it will need to be that other hard-coded alternative "Knowledge Base". I will get that adjusted for Tuesday's reference environment builds.

Comment by Carole Godfrey [ 15/Jun/20 ]

Sounds good – thanks David Crossley

Comment by Carole Godfrey [ 18/Jun/20 ]

David Crossley – just to mention – I added a separate related ticket in this area – it is due to migration script changes which added a Dummy Credentials
https://folio-org.atlassian.net/browse/FOLIO-2652

Comment by David Crossley [ 22/Jun/20 ]

All done now.

Generated at Thu Feb 08 23:21:59 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.