[FOLIO-1315] mechanism to consume tenant config at runtime Created: 27/Jun/18  Updated: 07/Feb/19

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

Type: Task Priority: P3
Reporter: Jakub Skoczen Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: build-release, ci, sprint41, sprint42, sprint43, sprint44, sprint45, ui-core
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-1314 review the folio-install single serve... Closed
Relates
relates to FOLIO-1450 Revise FOLIO release and deployment p... Open
relates to FOLIO-1314 review the folio-install single serve... Closed
Sprint:
Development Team: Core: Platform

 Description   

Rather than build-time which forces the system operator to build stripes platform from source every time.

Matthew Jones will provide more information.

Overview

Given the desire to publish pre-built UI bundles for download, it becomes necessary to apply tenant configuration post-build. The short term approach described in FOLIO-1314 Closed is to directly update tenant data in the bundle, like tenant ID and Okapi URL, via string replacement. This approach is suitable for basic bootstrapping, but does not account for other tenant-specific data like branding.

A longer-term solution would formally extract the (non-app) tenant information out of the dynamically generated stripes-config virtual module and then reapply it later. Extraction may consist of a Webpack dll or other splitting technique that would more readily permit modifying the tenant artifacts without full rebuild from source of the primary application. When considering something like themes, this approach may also be desirable to avoid full platform rebuild to say, simply change a color. Alternatively, the tenant config could be fetched at run-time from a static config deployed beside the bundle.

It is understood that these approaches do not attempt to address tenant-level app modifications. That is, a tenant wishing to download a previously built bundle and add or remove an app would not be able to do so without wither building from source or implementing a bundle generation service first.


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