[jboss-jira] [JBoss JIRA] (WFCORE-3991) read-provisioning-config management operation

[Alexey Loubyansky (JIRA)]

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

Alexey Loubyansky moved EAP7-1076 to WFCORE-3991:
-------------------------------------------------

                             Project: WildFly Core  (was: EAP 7 Planning Pilot)
                                 Key: WFCORE-3991  (was: EAP7-1076)
                          Issue Type: Feature Request  (was: Requirement)
                            Workflow: GIT Pull Request workflow   (was: EAP Agile Workflow 2.0)
                         Component/s: Management
                                      Server
                                          (was: Management)
                                          (was: Server)
          Jirban PT Pre-Checked (PC):   (was: TODO)
       Jirban PT Community Docs (CD):   (was: TODO)
         Jirban PT Product Docs (PD):   (was: New)
             Jirban PT Test Dev (TD):   (was: TODO)
        Jirban PT Docs Analysis (DA):   (was: TODO)
            Jirban PT Test Plan (TP):   (was: TODO)
    Jirban PT Analysis Document (AD):   (was: TODO)


> read-provisioning-config management operation
> ---------------------------------------------
>
>                 Key: WFCORE-3991
>                 URL: https://issues.jboss.org/browse/WFCORE-3991
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Management, Server
>            Reporter: Alexey Loubyansky
>            Assignee: Alexey Loubyansky
>
> Currently we have read-feature-description management operation which returns descriptions of available provisioning features, which is the basis for Galleon feature spec generation.
> I would like to add another operation that will describe the current state of the management model in terms of provisioning features (for both standalone and domain modes). The result of this operation will be used to identify user configuration changes since the last provisioned state, which will have to be done for basically any provisioning operation (such as applying patches, installing updates, etc).
> I would like to have it in EAP 7.2 even if Galleon patching is postponed to a 7.3. This feature will still allow us to upgrade from 7.2 to 7.3.



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