Initialize modules
Description
Environment
Potential Workaround
blocks
relates to
Checklist
hideTestRail: Results
Activity

Heikki LevantoJanuary 18, 2017 at 2:41 PM
Simple imoplementation done. Doing it the right way is in Okapi-238, so closing this one.

Heikki LevantoJanuary 18, 2017 at 2:39 PM
The stuff about system interfaces has got its own issue, Okapi-238. Continue the discussion there.

Heikki LevantoJanuary 18, 2017 at 2:29 PM
Later, we will have problems in accessing the interfaces Okapi does not know about (like admin of RMB modules). There we will have to be careful about many things, for example permissions, and of the admin function applies to any running instance of the module, any one instance, or all instances...

Heikki LevantoJanuary 18, 2017 at 2:17 PM
And I think we can implement this today, if we keep the tenantInterface field as a temporary, deprecated, way of specifying the same thing. That way, both forms of ModuleDescriptors would work. Later, when we make other breaking changes, we can drop the tenantInterface.

Heikki LevantoJanuary 18, 2017 at 2:15 PM
Hmm, the discussion on Slack seems to like the idea of these specially defined 'provides' interfaces. Mostly because there will be more of them. We have talked about a health check, the RMB already defines some kind of admin interface for setting a log level, and who knows what else, as well as some way to get database statistics...
Details
Assignee
Heikki LevantoHeikki LevantoReporter
Heikki LevantoHeikki LevantoLabels
Priority
P2TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee

Reporter

Modules need to be initialized when enabled for a tenant