Details
-
Umbrella
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
Description
Currently we provide certain things (like e.g database connection info, okapi url, etc) in a module implementation specific way. We need to standardize on methods supported across the platform. Some options include:
- env vars
- command-line switches
- config file (e.g JSON) supplied to STDIN
We have also talked about a possiblity of a special
- init web service
invoked by okapi after module startup. But certain things like DB conn info or Okapi URL may be required before the module is able to handle requests so this is a less appealing option.
TestRail: Results
Attachments
Issue Links
- is blocked by
-
FOLIO-465 Align CI and demo/bb with envar based provisioning of configuration
-
- Closed
-
-
OKAPI-232 Initialize modules
-
- Closed
-
- relates to
-
METADATA-43 Move metadata modules to standardised module environment configuration
-
- Closed
-
-
OKAPI-240 module deployment properties
-
- Closed
-
-
METADATA-22 Create deployable Module Descriptor for inventory and inventory storage modules
-
- Closed
-