[
https://issues.jboss.org/browse/WFCORE-4135?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-4135:
------------------------------------------
The server successfully executing a management op and responding with reload-required, and
then the user does the reload but the change doesn't end up in the runtime -- that
would be a bug. If the server knows it won't be able to effect the change if reload is
invoked, then it shouldn't report the initial op as a success.
This could be done by having the OperationContext reject calls to reloadRequired() and
restartRequired(), instead marking itself as rollback only and throwing an
OperationFailedRuntimeException. The OperationContext would need to know the process is
configured this way though.
Thanks for the info about the use cases.
Add a new property to disable backups of configuration XML files.
Also avoid writing to standalone_xml_history when --read-only-server-config=<config>
is set.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: WFCORE-4135
URL:
https://issues.jboss.org/browse/WFCORE-4135
Project: WildFly Core
Issue Type: Feature Request
Components: Management
Reporter: Rafael Ruiz
We need something like
--disable-configuration-history
to use when running in containers to avoid write to any directory
('standalone_xml_history').
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)