Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
2.5.1
Description
POSTed a list like this to the /_/proxy/tenants/<tenantId>/install endpoint:
[
{
"id": "mod-codex-mux-1.2.1-SNAPSHOT.32",
"action": "enable"
},
{
"id": "folio_search-1.1.100035",
"action": "enable"
},
{
"id": "mod-codex-mock-1.0.2-SNAPSHOT.20",
"action": "enable"
},
{
"id": "mod-codex-inventory-0.0.3-SNAPSHOT.15",
"action": "enable"
}
]
Resulted in this:
[
{
"id": "mod-codex-mux-1.2.1-SNAPSHOT.32",
"action": "enable"
},
{
"id": "folio_search-1.1.100035",
"action": "enable"
},
{
"id": "mod-codex-mux-1.2.1-SNAPSHOT.32",
"action": "disable"
},
{
"id": "mod-codex-mock-1.0.2-SNAPSHOT.20",
"action": "enable"
},
{
"id": "mod-codex-inventory-0.0.3-SNAPSHOT.15",
"action": "enable"
}
]
Note that mod-codex-mux is first enabled, then disabled. All three "codex" modules provide the codex-2.0 interface, mod-codex-mock and mod-codex-inventory both as a "multiple"-type interface.
If I change the order of the original request to put mod-codex-inventory and mod-codex-mock before mod-codex-mux, I get the expected result (all three modules enabled).
Not sure if this is a bug or intended behavior, I found it a little unintuitive.
TestRail: Results
Attachments
Issue Links
- blocks
-
FOLIO-1010 Include Codex backends in snapshot builds
-
- Closed
-
- relates to
-
-
- Closed
-
