Now that we have the agent plugins disable and enable features, it should be possible to display the installed plugins from this page.
I think it may be enough to run the "plugins info" operation.
It is important to show the name that is the one to be entered in the "rhq.agent.plugins.enabled" property, so that it is consistent with what the user enters in that property.
See also Bug 536287
Running the agent operation, waiting for the results and then rendering the UI can be potentially slow. Bug 1022943 copes with a similar issue (both would benefit from having the records about what agent has what plugins (+versions) installed/enabled).
I'll implement a prototype using the ispn for storing the results of the "plugins info" op. in order to wait only for the first call. Consequent calls will be cached.
time: 2014-02-27 19:47:06 +0100
author: Jirka Kremser - firstname.lastname@example.org
message: [BZ 1065680] - Agent admin page should list the installed plugins -
Implementing new method on TopologyManagerBean for obtaining
the corresponding resource id for an agent instance. If there
is such an id, web UI runs the "retrieveAllPluginInfo"
operation and displays its result in the agent admin UI (on the
agent detail page). So the assumption here is that the agent
has already imported the RHQ Agent resource.
Not using the infinispan, because cache would introduce inconsistency.
Until we require agent in the inventory (or have a separate "admin" inventory for stuff like agent, storage nodes, etc, that would mandatorily include the agent), I am not sure how useful this feature is, because having the agent in the inventory is not mandatory.
Also this functionality is only available using the UI and not exposed remotely either via REST or remote API (ideally both).
Right, having the agent in the (separate "admin" or just normal) inventory by default it would be much simpler. However, it is not the case and now the UI just shows additional info if you have the agent committed. If we assume the agent to be in the (admin) inventory (in the future perhaps), nothing needs to be changed in coregui.
The functionality is exposed also via CLI and REST using the agent operation "retrieveAllPluginInfo". I've added a flag there that says whether the agent plugin is enabled or not.
Bulk closing of 4.10 issues.
If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.