Details
-
New Feature
-
Status: Open (View Workflow)
-
P4
-
Resolution: Unresolved
-
None
-
None
-
-
CP: ready for planning
-
3
-
Core: Platform
Description
In module descriptor sharing, it seems like there is a use case for filtering the module descriptors you pull from a remote registry, so that only the modules (and potentially, specific module versions) that you are interested in offering to your tenants are in a local registry.
One way to achieve this might be to use some of the same query parameters that are available on the /_/proxy/modules endpoint, namely filter, latest, npmSnapshot, preRelease, provide, require, and scope.
TestRail: Results
Attachments
Issue Links
- relates to
-
FOLIO-1822 SPIKE: Investigate ways to improve use of folio-registry of ModuleDescriptors
-
- Open
-
-
FOLIO-2117 Kubernetes integration (Q2, containerization)
-
- Closed
-
-
FOLIO-2118 CI-integrated continuous deployment (Q2, cluster setup)
-
- Closed
-
-
OKAPI-727 Optimize pull and introduce incremental parameter
-
- Closed
-
-
OKAPI-1002 module tags
-
- Open
-
-
UXPROD-1823 Kubernetes integration (Q3, Okapi features)
-
- Draft
-
-
UXPROD-1827 CI-integrated continuous deployment (Q3, FOLIO setup)
-
- Closed
-