Bug 1309480 - Remote API is missing ability to retrieve and revert historic plug-in and resource configuration
Summary: Remote API is missing ability to retrieve and revert historic plug-in and res...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: CLI
Version: JON 3.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: One-off release
Assignee: Michael Burman
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 1309481
TreeView+ depends on / blocked
 
Reported: 2016-02-17 22:58 UTC by Larry O'Leary
Modified: 2019-11-14 07:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1309481 (view as bug list)
Environment:
Last Closed: 2018-09-13 15:01:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2169271 0 None None None 2016-02-17 23:21:26 UTC

Description Larry O'Leary 2016-02-17 22:58:47 UTC
Description of problem:
ConfigurationManagerRemote interface does not expose a method to apply/revert configuration from configuration history/updates.

This prevents a client from using the remote API to manage configuration for a resource and its connection settings based on prior configuration updates.

Version-Release number of selected component (if applicable):
3.1.2

How reproducible:
Always

Steps to Reproduce:
1.  Import a resource.
2.  Make configuration changes.
3.  Use the remote API to retrieve the resource's plug-in configuration updates:

> // Get all plugin configuration updates for the Resource myResource
> var myConnectionHistory = myResource.getPluginConfigurationUpdates();


Actual results:
myConnectionHistory contains a list of ids but there is no way to get the configuration update record showing the date/time of the update along with who applied it and its status along with the actual Configuration object so that it can be reapplied to the resource.

Expected results:
myConnectionHistory should contain a list of PluginConfigurationUpdate which includes all the details of the update including Configuration.

Additionally, it should be possible to pass a resource ID and configuration update ID to a method of ConfigurationManager to have the server reapply the desired configuration update. This would be similar to the Rollback function provided in the configuration history pages of the UI.

Additional info:
It appears that some/all of this functionality is exposed in the local interface so perhaps this is just a matter of moving local methods over to the remote interface.

Comment 3 Filip Brychta 2018-09-13 15:01:11 UTC
Triage: Larry, Simeon, Filip - closing as won't fix because this issue was fixed in 3.3.6 bz1309481


Note You need to log in before you can comment on or make changes to this bug.