[jboss-jira] [JBoss JIRA] (WFCORE-3167) option to filter out aged out patches from the patching history

Brian Stansberry (JIRA) issues at jboss.org
Sun Oct 29 15:17:04 EDT 2017


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

Brian Stansberry updated WFCORE-3167:
-------------------------------------
    Fix Version/s: 4.0.0.Alpha3
                       (was: 4.0.0.Alpha2)


> option to filter out aged out patches from the patching history
> ---------------------------------------------------------------
>
>                 Key: WFCORE-3167
>                 URL: https://issues.jboss.org/browse/WFCORE-3167
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: CLI, Patching 
>    Affects Versions: 3.0.0.Beta30
>            Reporter: Alexey Loubyansky
>            Assignee: Alexey Loubyansky
>             Fix For: 4.0.0.Alpha3
>
>
> show-history management operation (and patch history cli command) returns all the patches that have been applied to the installation even if some of them have been aged out by executing ageout-history management operation.
> In some cases it would be useful to filter out the aged out patches from the result, leaving only the patches that can actually be rolled back by a user.
> That could be achieved by adding an optional boolean parameter exclude-agedout (with default value false to preserve the current behavior) to show-history operation.
> The high level CLI command patch history could include an equivalent --exclude-agedout argument.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jboss-jira mailing list