[
https://issues.jboss.org/browse/WFCORE-334?page=com.atlassian.jira.plugin...
]
Brian Stansberry resolved WFCORE-334.
-------------------------------------
Resolution: Won't Fix
This isn't practical on the server side, and if it isn't done server-side it
won't help the CLI batch case, which AIUI is the goal.
Ignoring a failure in a batch means discarding any interim changes that op made before the
failure was detected and proceeding as if the op never existed. That cannot be done
feasibly in any sort of consistent manner. Consistent meaning always works, not just for
certain cases where the op failed before making any changes.
"Ignore failure" for management operations
------------------------------------------
Key: WFCORE-334
URL:
https://issues.jboss.org/browse/WFCORE-334
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Reporter: Ondrej Zizka
Most operations don't follow any "overwrite" concept.
To emulate it, one needs to check for existence of a resource, conditionally delete it,
and then create the new one.
This is not easily applicable in a batch.
Implementing overwrite for all actions would be tedious.
But this could help:
Another "standard" property (similar to {{address}} and {{op-name}})
"onFail=ignore" or such, which would make the operation not fail if an exception
occurs. A short CLI syntax could be a '?' at the end of operation's name:
{code}
/foo=bar/boo=baz:remove?()
{code}
This would allow mgmt API users to queue a removing operation without knowing if it
exists; thus, effectively, doing an overwrite.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)