/about should report on enabled modules and/or installed modules
Description
Environment
Potential Workaround
is duplicated by
relates to
Checklist
hideTestRail: Results
Activity
Wayne Schneider October 26, 2017 at 12:48 PM
@Mike Taylor – see FOLIO-906 for enabling the module in the blackbox. Hopefully I'll get to that today.
Mike Taylor October 26, 2017 at 10:41 AM
Good call on the use of colour. But (A) as you say, grey seems like it's going to be pretty universal in this kind of context (like the main font colour but less so); and (B) worrying about the varying cultural connotations of different colours is a bit of a luxury problem as we race towards the v1 deadline.
Down the line, I guess we will have a set of semantic colour codes, whose actual colours will be defined on a locale-specific basis; and code using them will look like <div class="color-warning">That module is not enabled here<div>. But it's a problem for another day.
Zak Burke October 26, 2017 at 10:37 AM
Second, I was thinking of a discussion we had in Montreal about internationalization and how color signifiers we are used to aren't necessarily universal, e.g. "green" doesn't always mean "go"; sometimes "blue" means "go" or something like that, so I was aiming for something unambiguous. That said, I agree it's a bit much and grey works for me.
Mike Taylor October 26, 2017 at 10:34 AM
Right, I thought this seemed familiar.
Presumably, in future VMs, this misconfiguration of the tenant will be fixed and it will Just Work – right, @Wayne Schneider?
Zak Burke October 26, 2017 at 10:32 AM
First, the GET 404 is the result of your tenant not having permissions on the okapi module; see FOLIO-906. Send a POST request to http://localhost:9130/_/proxy/tenants/diku/modules with the body
{
"id": "okapi-2.0.1"
}substituting in the correct version for your okapi module.
/aboutreferences:9130/_/proxy/modules(which tells you which modules are globally installed), rather than, say,:9130/_/proxy/tenants/<tenantId>/modules(which tells you which modules are actually enabled for the current tenant).From the point of view of a tenant, a disabled module is effectively unavailable, so reporting only whether it’s installed seems disingenuous, or at best irrelevant, if it’s not enabled. Maybe there should be two about pages, one showing what’s installed on the cluster and one showing what’s enabled for the current tenant?