[
https://issues.jboss.org/browse/WFCORE-2219?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-2219:
------------------------------------------
If this is done via a command line switch, possibly the same switch could drive whether
boot is lenient in non-admin-only mode about Stage.RUNTIME failures.
--boot-validation=LENIENT | STRICT
We're currently LENIENT in both admin-only and normal mode, so it's possible to
add this without breaking either thing.
I don't know if it's wise to use a single param to control two slightly different
things though. But if we want to, then we should use it for both from the start, otherwise
we introduce a behavior change when we bring it in for the 2nd behavior.
Ability to turn off boot time capability resolution leniency in
admin-only mode
-------------------------------------------------------------------------------
Key: WFCORE-2219
URL:
https://issues.jboss.org/browse/WFCORE-2219
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Currently boot is lenient about broken capability requirements during admin-only boot. We
need a way to turn this off.
The current behavior is a fine default, as it allows users to boot a broken config in
--admin-only and then fix the config. Without this the user is forced to rely on xml
editing.
But there are other use cases for admin-only, for example in automated provisioning
systems or testing systems, where the user can quite reasonable want a broken config
immediately generate an boot failure, as the automated system is not designed to handle
incorrect initial input.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)