[jboss-jira] [JBoss JIRA] (WFCORE-2219) Ability to turn off boot time capability resolution leniency in admin-only mode

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFCORE-2219:
-------------------------------------
    Description: 
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 reasonably want a broken config to immediately generate a boot failure, as the automated system is not designed to handle incorrect initial input.



  was:
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 to immediately generate a boot failure, as the automated system is not designed to handle incorrect initial input.





> 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 reasonably want a broken config to immediately generate a 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)