[FOLIO-926] Explicitly set port mappings for docker containers in deployment descriptor Created: 06/Nov/17  Updated: 12/Nov/18  Resolved: 11/Dec/17

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

Type: Task Priority: P2
Reporter: John Malconian Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: ci, sprint26
Remaining Estimate: Not Specified
Time Spent: 3 hours
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-886 add java remote debugging as standard... Closed
Sprint:

 Description   

The new base images for all backend modules include additional ports for remote JMX. Therefore, it is necessary to explicitly include the Docker port mapping to the application for the container that Okapi deploys in the deployment descriptor. By default, Okapi picks the lowest exposed port which is not desired. Add the port mapping to the deployment descriptors used by folio-ansible for each backend module.



 Comments   
Comment by John Malconian [ 06/Nov/17 ]

See OKAPI-458 Closed for additional details. The latest released version of Okapi includes this feature.

Comment by Wayne Schneider [ 06/Nov/17 ]

This does pose a challenge for automated deployment from the dependencies required by a Stripes platform. We could include the launch descriptor in the published module descriptor, perhaps.

Comment by Wayne Schneider [ 11/Dec/17 ]

Deployment descriptors now use the "dockerArgs" key to set the port that Okapi should proxy.

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