| Table of Contents |
|---|
...
- Apparently it's not possible to specify a dependency on a multiple interface, so clients will need to.
- It might be helpful to extend/enhance some of the OKAPI APIs for querying interfaces
- Extending the provides query to allow the specification of a version could be helpful, e.g.
/_/proxy/modules?provide=distributed_configuration:2.0&scope=orders
Possible JIRA needed - Extending
/_/proxy/tenants/{tenant}/interfacesmay also make sense Possible JIRA needed
- Extending the provides query to allow the specification of a version could be helpful, e.g.
- If the interface is being changed often it could become a pain for modules which require the distributed_configuration interface. As a point of reference, mod-configuration's configuration interface has been at 2.0 for 4 years now, so it seems unlikely that we'll need to change this frequently.
...
- A naming convention will likely help here.
- scope is an array, so maybe it should be a list of the interfaces provided by the module, or at least those which store configuratioconfiguration
What about business logic modules?
...