[FOLIO-2675] Make the Okapi URL and Tenant ID be external from the stripes bundle build Created: 02/Jul/20  Updated: 17/Aug/20

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

Type: Task Priority: P3
Reporter: Taras Spashchenko Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: dev-environment
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-2624 SPIKE: Build and deploy Stripes bund... Closed
relates to FOLIO-2601 PoC for hosted development environmen... Closed
Sprint:

 Description   

These changes are required only for hosted development environments builds.

Currently, Okapi URL and Tenant ID parameters are applied at the build time of a docker image for the Stripes Application. It means that for every new tenant in the hosted development environment a team has to build a Stripes docker image from scratch and can't reuse existing one even if a set and versions of UI modules did not change.

The solution here could be to modify the docker image for UI the way that at the build time some placeholders should be used for Okapi URL and Tenant ID.
At the runtime though when a docker container starts those placeholders could be replaced with real values provided as environment variables.



 Comments   
Comment by Jakub Skoczen [ 06/Jul/20 ]

Wayne Schneider John Malconian jroot

We discussed that the ability to configure OkapiURL and TenantId might be useful for container bundles that are based on "releases" (like the Goldenrod release) or "snapshots" (master branches) but it won't be useful for team envs because each team will want to create their own bundle with select modules running from feature branches.

Comment by Jakub Skoczen [ 17/Aug/20 ]

Unlinking from the team env PoC epic.

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