New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WFCORE-671 : Configuration change reporting. #890
Conversation
Core - Full Integration Build 1324 is now running using a merge of 4e869ff |
Linux Build 2187 is now running using a merge of 4e869ff |
Windows Build 1714 is now running using a merge of 4e869ff |
Windows Build 1714 outcome was SUCCESS using a merge of 4e869ff |
Linux Build 2187 outcome was SUCCESS using a merge of 4e869ff |
Core - Full Integration Build 1324 outcome was FAILURE using a merge of 4e869ff Build problems:Failed tests detected Failed tests
|
Core - Full Integration Build 1330 is now running using a merge of 4e869ff |
Windows Build 1721 is now running using a merge of 4a55c1a |
Linux Build 2193 is now running using a merge of 4a55c1a |
Core - Full Integration Build 1331 is now running using a merge of 4a55c1a |
Core - Full Integration Build 1330 outcome was FAILURE using a merge of 4a55c1a Build problems:Failed tests detected Failed tests
|
Windows Build 1721 outcome was FAILURE using a merge of 4a55c1a Build problems:Failed tests detected Failed tests
|
Linux Build 2193 outcome was SUCCESS using a merge of 4a55c1a |
Core - Full Integration Build 1331 outcome was SUCCESS using a merge of 4a55c1a |
Retest this please |
Linux Build 2196 is now running using a merge of 4a55c1a |
Windows Build 1724 is now running using a merge of 4a55c1a |
Core - Full Integration Build 1334 is now running using a merge of 4a55c1a |
Windows Build 1724 outcome was SUCCESS using a merge of 4a55c1a |
Linux Build 2196 outcome was SUCCESS using a merge of 4a55c1a |
Core - Full Integration Build 1334 outcome was FAILURE using a merge of 4a55c1a Build problems:Failed tests detected Failed tests
|
retest this please |
Windows Build 1758 is now running using a merge of 4a55c1a |
Core - Full Integration Build 1369 is now running using a merge of 4a55c1a |
Linux Build 2232 is now running using a merge of 4a55c1a |
|
||
@Override | ||
public void execute(OperationContext context, ModelNode operation) throws OperationFailedException { | ||
ModelNode maxHistory = MAX_HISTORY.resolveModelAttribute(context, operation); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't correct for a write-attribute op handler, which has params (name=max-history,value=15), not (max-history=15).
Windows Build 1758 outcome was SUCCESS using a merge of 4a55c1a |
Linux Build 2232 outcome was SUCCESS using a merge of 4a55c1a |
Core - Full Integration Build 1369 outcome was FAILURE using a merge of 4a55c1a Build problems:Failed tests detected Failed tests
|
d9eaea9
to
6a62f8b
Compare
Windows Build 1766 is now running using a merge of 6a62f8b |
Linux Build 2241 is now running using a merge of 6a62f8b |
Core - Full Integration Build 1377 is now running using a merge of 6a62f8b |
Windows Build 1766 outcome was SUCCESS using a merge of 6a62f8b |
Linux Build 2241 outcome was SUCCESS using a merge of 6a62f8b |
Core - Full Integration Build 1377 outcome was FAILURE using a merge of 6a62f8b Build problems:Failed tests detected Failed tests
|
Adding new collector Creating a resource for configuration-changes configuration. Securing operations : * if the user can't access the resource addressed by the operation then the operation information are not displayed but the entry point is kept (aka date, result). * if the user can access the address but doesn't have the rights to run the operation then the parameters are not accessible in the operation description.
Providing an in-memory audit-logger to track configuration changes easily.
Linux Build 2256 is now running using a merge of 43b4015 |
Windows Build 1779 is now running using a merge of 43b4015 |
Core - Full Integration Build 1395 is now running using a merge of 43b4015 |
|
||
public static final String OPERATION_NAME = "show-logs"; | ||
protected static final AttributeDefinition[] ATTRIBUTES = new AttributeDefinition[]{MAX_OPERATION_COUNT}; | ||
private static final Map<String, InMemoryAuditLogHander> histories = Collections.synchronizedMap(new HashMap<String, InMemoryAuditLogHander>()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't want to delay merging this PR for this, but once it's merged please send up a PR to make this a non-static field and have the InMemoryAuditLogHandlerResourceDefinition pass a ref to it to the handlers when it constructs them.
Having this be static is no big deal in this case, but I don't want anyone looking at kernel code and thinking that using static fields to store state is a good practice.
Windows Build 1779 outcome was FAILURE using a merge of 43b4015 Build problems:Failed tests detected Failed tests
|
Linux Build 2256 outcome was SUCCESS using a merge of 43b4015 |
Core - Full Integration Build 1395 outcome was FAILURE using a merge of 43b4015 Build problems:Failed tests detected Failed tests
|
WFCORE-671 : Configuration change reporting.
[JBEAP-19670][WCORE-5014] Remove the PropertySorter and specially handle the file …
Adding new collector
Creating a resource for configuration-changes configuration.
Securing operations :
* if the user can't access the resource addressed by the operation then the operation information are not displayed but the entry point is kept (aka date, result).
* if the user can access the address but doesn't have the rights to run the operation then the parameters are not accessible in the operation description.
Providing an in-memory audit-logger to track configuration changes easily.
Jira: https://issues.jboss.org/browse/WFCORE-671