[FOLIO-1659] folio-ansible: Configure mod-graphql to read mod-inventory-storage RAML/JSON Created: 14/Dec/18  Updated: 03/Jun/20  Resolved: 05/Jan/19

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

Type: New Feature Priority: P3
Reporter: Wayne Schneider Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: ci, sprint54
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:

 Description   

mod-graphql needs to be configured with the RAML and JSON schema of mod-inventory-storage in order to query that module for data. Currently, that configuration is done by directing the module to read files from the startup command line.

The version of the RAML needs to be in sync with the running version of mod-inventory-storage.

Whatever solution we come up with is temporary, as ultimately mod-graphql will be able to use an API to get what it needs at runtime.



 Comments   
Comment by Wayne Schneider [ 14/Dec/18 ]

Possible solutions, not really in order:

  • Copy the needed files into the mod-graphql Docker image when it is built by CI, and change the Docker CMD directive to load them on module startup
  • Rebuild the mod-graphql Docker image locally before it is deployed with the needed files and command line
  • Make the files available on the host as a Docker volume and configure the container to give it access (and launch with an updated command line)

Other thoughts, John Malconian?

Comment by Mike Taylor [ 14/Dec/18 ]

Should mention the fourth option:

Since the present issue turns out not to be trivial as I had hoped, that might be the best.

Comment by Wayne Schneider [ 04/Jan/19 ]

The Dockerfile has been updated to launch mod-graphql with the appropriate command line to read the RAML files from the container. The container is not answering on the mapped port, so there is still something amiss.

Comment by Wayne Schneider [ 05/Jan/19 ]

The Dockerfile and module descriptor were mapping the wrong port (3000 instead of 3001).

Comment by Mike Taylor [ 05/Jan/19 ]

All working nicely now!

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