Details
-
Umbrella
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
customfield_11100 19775
-
Core: Platform
Description
We have discussed the following extensions to the tenant and Okapi install calls:
- a new version of the tenant init call that allows specifying the initialisation properties. This will allow us to control if and what kind of data is loaded during init (reference on/off, sample on/off, etc), By default only reference data will be loaded in the first version of the RMB implementation.
- extension to the Okapi's install call to provide the global values for the initialisation properties. Those values would then be passed on to the individual modules during the init call.
In the first phase we will address the implementation of this new functionality in mod-inventory-storage.
Open questions:
- should Okapi store the init props and resend them during module upgrade?
- should we have an initial set of default init props that can be specified before any install call?
Reference data
The name of the parameter that controls reference data loading is loadReference with true|false (both in the tenantParams string query param and in the parameters kv array in the moduleInfo payload)
By default the value of loadReference is false
Sample data
The name of the parameter that controls sample data loading is loadSample with true|false (both in the tenantParams string query param and in the parameters kv array in the moduleInfo payload)
By default the value of loadSample is false
TestRail: Results
Attachments
Issue Links
- blocks
-
FOLIO-1577 Automated builds for FOLIO 'release'
-
- Closed
-
-
FOLIO-2118 CI-integrated continuous deployment (Q2, cluster setup)
-
- Closed
-
-
UXPROD-1827 CI-integrated continuous deployment (Q3, FOLIO setup)
-
- Closed
-
- is blocked by
-
FOLIO-1681 folio-ansible: Use tenant init to load inventory storage reference data
-
- Closed
-
-
OKAPI-682 Tenant init parameters
-
- Closed
-
-
OKAPI-688 tenant ref problem: own module not available at tenant init phase
-
- Closed
-
- relates to
-
CIRCSTORE-103 use loadSample to load sample data
-
- Closed
-
-
CIRCSTORE-104 use loadReference to load reference data
-
- Closed
-
-
FOLIO-1862 SPIKE: consider loadSample/loadReference = "once"
-
- Open
-
-
MODINVSTOR-216 load reference data as part of the tenant init call
-
- Closed
-
-
MODINVSTOR-264 use loadSample to load sample data
-
- Closed
-
-
MODORDSTOR-48 Rework how sample data is loaded
-
- Closed
-
-
MODTAG-14 use loadReference to load reference data
-
- Closed
-
-
MODTAG-15 use loadSample to load sample data
-
- Closed
-
-
MODUSERS-103 use loadSample/loadReference to load sample and reference data
-
- Closed
-
-
UXPROD-1815 support for upgrading schemas without complete reload of data (DB migrations) - PoC + devops guide
-
- Closed
-
-
UXPROD-2120 support for upgrading schemas without complete reload of data (DB migrations) - rollout + devops
-
- In progress
-
-
FOLIO-1548 SPIKE: a lighter-weight folio/testing-backend VM
-
- Closed
-
-
FOLIO-1726 enable sample MARC record data loading in mod-source-record-storage
-
- Closed
-
-
FOLIO-2118 CI-integrated continuous deployment (Q2, cluster setup)
-
- Closed
-
-
MODVEND-81 Load sample data via tenant API
-
- Closed
-
-
OKAPI-655 Module scripting (e.g to support data loading)
-
- Closed
-
-
RMB-296 tenant init for loading reference data
-
- Closed
-
-
UXPROD-753 live db upgrades (db migration)
-
- Closed
-
-
UXPROD-1508 Populate reference data as part of initial migration
-
- Closed
-
-
UXPROD-1827 CI-integrated continuous deployment (Q3, FOLIO setup)
-
- Closed
-
-
UXPROD-2612 MARC Authority record - Load sample data
-
- Closed
-