[FOLIO-1750] include edge-orders in folio-snapshot/testing Created: 28/Jan/19 Updated: 03/Jun/20 Resolved: 04/Apr/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Jakub Skoczen | Assignee: | Ian Hardy |
| 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 60 | ||||||||||||||||||||||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||||||||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||||||||||||||||||||||||||
| Description |
|
Deploy edge-orders in folio-snapshot and folio-testing. |
| Comments |
| Comment by Craig McNally [ 04/Mar/19 ] |
|
Moving from Blocked to Open now that
$ 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 Ann-Marie Breaux (Inactive) [ 20/Mar/19 ] |
|
Hi Jakub Skoczen just checking on this request - do you have an idea when this might show in folio-testing? We're anxious to get this all hooked up, and it will make an excellent demo - starting on a vendor site, having the order created in FOLIO, and then having the Inventory records created by the Order app. Once this is released, we'll need core-fxn to supply the URL to the edge API and an API key, so that we can condition the sender side with that info. We've already got this hooked up in an EBSCO environment, so copying Craig McNally in case you have any technical or implementation questions. |
| Comment by Ian Hardy [ 04/Apr/19 ] |
|
This should go into tonight's build. The API key will be apikey: eyJzIjoiNXNlNGdnbXk1TiIsInQiOiJkaWt1IiwidSI6ImRpa3UifQ== |
| Comment by Ann-Marie Breaux (Inactive) [ 04/Apr/19 ] |
|
Stellar, thank you so much Ian Hardy. Can't wait to try it out!! |
| Comment by Craig McNally [ 04/Apr/19 ] |
|
Something doesn't seem right Ian Hardy... I can place an order directly to mod-gobi, but get an error when doing so via the edge API... $ curl "http://folio-testing-backend01.aws.indexdata.com:9130/gobi/orders" -XPOST -H "Content-type: application/xml" --data-binary @src/test/resources/GOBIIntegrationServiceResourceImpl/po_listed_print_monograph.xml -w '\n' -H "X-Okapi-Token: $TOKEN" <?xml version="1.0" encoding="UTF-8" standalone="yes"?><Response><PoLineNumber>10039-1</PoLineNumber></Response> $ curl "folio-testing-backend01.aws.indexdata.com:8000/orders?type=gobi" -H "Authorization: apikey eyJzIjoiNXNlNGdnbXk1TiIsInQiOiJkaWt1IiwidSI6ImRpa3UifQ==" -XPOST -H "Content-type: application/xml" --data-binary @src/test/resources/GOBIIntegrationServiceResourceImpl/po_listed_print_monograph.xml -w '\n'
<?xml version='1.0' encoding='UTF-8'?>
<Response>
<Error>
<Code>INTERNAL_SERVER_ERROR</Code>
<Message>Failed to convert FOLIO response to XML</Message>
</Error>
</Response>
However, the API key seems to work: $ curl "folio-testing-backend01.aws.indexdata.com:8000/orders/validate?type=gobi" -H "Authorization: apikey eyJzIjoiNXNlNGdnbXk1TiIsInQiOiJkaWt1IiwidSI6ImRpa3UifQ==" -XPOST <test>POST - OK</test> $ curl "folio-testing-backend01.aws.indexdata.com:8000/orders/validate?type=gobi" -H "Authorization: apikey eyJzIjoiNXNlNGdnbXk1TiIsInQiOiJkaWt1IiwidSI6ImRpa3UifQ==" -XGET <test>GET - OK</test> |
| Comment by Ann-Marie Breaux (Inactive) [ 04/Apr/19 ] |
|
Thank you for doing some testing and investigating, Craig McNally. Ian Hardy is it possible to triage this quickly? Do we need a separate bug story for it? Please let me know ASAP. |
| Comment by Craig McNally [ 04/Apr/19 ] |
|
I think Kruthi Vuppala found the issue... it's a permission issue with mod-orders. I'm going to create a P1 bug for this and will link it here afterwards |
| Comment by Ian Hardy [ 04/Apr/19 ] |
|
This is done. There was a permissions bug in mod orders that needed fixing:
|