[FOLIO-1748] include edge-rtac in folio-snapshot/testing Created: 28/Jan/19 Updated: 03/Jun/20 Resolved: 22/Mar/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Jakub Skoczen | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||
| Sprint: | Core: Platform - Sprint 59 | ||||||||||||||||||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||||||||||||||||||||||
| Description |
|
Deploy edge-rtac in folio-snapshot and folio-testing. |
| Comments |
| Comment by Craig McNally [ 04/Mar/19 ] |
|
See https://github.com/folio-org/edge-common/releases/tag/v2.0.1 $ java -jar target/edge-common-api-key-utils.jar -g -t diku -u diku_admin
eyJzIjoiYlNXMkZhRWpMaSIsInQiOiJkaWt1IiwidSI6ImRpa3VfYWRtaW4ifQ==
$ java -jar target/edge-common-api-key-utils.jar -p eyJzIjoiYlNXMkZhRWpMaSIsInQiOiJkaWt1IiwidSI6ImRpa3VfYWRtaW4ifQ==
Salt: bSW2FaEjLi
Tenant ID: diku
Username: diku_admin
$ echo eyJzIjoiYlNXMkZhRWpMaSIsInQiOiJkaWt1IiwidSI6ImRpa3VfYWRtaW4ifQ== | base64 --decode
{"s":"bSW2FaEjLi","t":"diku","u":"diku_admin"}
|
| Comment by Wayne Schneider [ 21/Mar/19 ] |
|
Craig McNally can I get a basic description of the API so I can validate that the module is working? |
| Comment by Craig McNally [ 21/Mar/19 ] |
|
It's in the API docs... https://s3.amazonaws.com/foliodocs/api/edge-rtac/edge-rtac.html# From the edge-rtac README:
Some of that mimicry turned out to be unnecessary and can be dispensed with (e.g. the API path). I lament that has not already been cleaned up. Hopefully we can get to it before go-live and the rest documented ASAP. |
| Comment by Wayne Schneider [ 21/Mar/19 ] |
|
edge-rtac and mod-rtac have been configured for the folio-testing and folio-snapshot builds, and should appear in the reference environments after tonights builds. |
| Comment by Craig McNally [ 21/Mar/19 ] |
|
|
| Comment by Craig McNally [ 21/Mar/19 ] |
|
have the URL/API key been documented anywhere yet? |
| Comment by Wayne Schneider [ 21/Mar/19 ] |
|
No...the urls will be: And the institutional user is diku. I'm not sure where to document this; any ideas? |
| Comment by Wayne Schneider [ 22/Mar/19 ] |
|
Verified in folio-testing: <?xml version='1.0' encoding='UTF-8'?> <holdings> <holding> <id>bb5a6689-c008-4c96-8f8f-b666850ee12d</id> <callNumber>D15.H63 A3 2002</callNumber> <location>SECOND FLOOR</location> <status>Checked out</status> <dueDate>2017-01-19T12:42:21.000+0000</dueDate> </holding> </holdings> |
| Comment by Craig McNally [ 22/Mar/19 ] |
No, I'm not sure either. Maybe https://dev.folio.org/guides/automation/ ? |
| Comment by Wayne Schneider [ 23/Mar/19 ] |
|
Good idea – see
|