Details
Description
Add CLI support to dynamically deploy, enable, and upgrade any necessary modules for a platform in Okapi.
Start with dedicated stand-alone command(s) for module installation that can be optionally invoked via the build command (omitting this part to reduce complexity of combining two very different commands into one). Module installation should be an optional step, allowing for the existing build command to operate as-is.
Okapi guide: https://github.com/folio-org/okapi/blob/master/doc/guide.md
TestRail: Results
Attachments
Issue Links
- blocks
-
FOLIO-1548 SPIKE: a lighter-weight folio/testing-backend VM
-
- Closed
-
- is blocked by
-
FOLIO-1632 Create lighter-weight folio core VM
-
- Closed
-
-
STCLI-111 Incorrect stripes-core reported with mod descriptor command
-
- Closed
-
- relates to
-
STCLI-114 CLI support for local backend modules
-
- Closed
-
-
STCLI-115 Gather permissions for a platform
-
- Closed
-
-
STCLI-116 Support mod install JSON output as input
-
- Closed
-
-
STCLI-117 Support okapi/tenant values from stripes.config.js for okapi-based commands
-
- Closed
-
-
FOLIO-1633 Establish scheme for declaring additional backend modules within a platform
-
- Open
-
-
FOLIO-1730 Create folio/minimal Vagrant box
-
- Open
-
-
STCLI-127 Support multiple module descriptors with "mod add"
-
- Closed
-
-
UXPROD-1156 Re-organization of the CI/CD environments and dev boxes
-
- Closed
-
-
UXPROD-1424 Re-organization of the CI/CD environments and dev boxes pt 2
-
- Closed
-