[jboss-jira] [JBoss JIRA] (WFCORE-1752) The deployment-overlay command fails to redeploy affected deployments

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13348084#comment-13348084 ] 

Brian Stansberry commented on WFCORE-1752:
------------------------------------------

And for myself. :) It was kind of a brainstorming question.  A deployment-overlay resource could certainly have a "redeploy-affected" operation where it works out the set of affected deployments and adds steps to redeploy them. The full set of deployments, their runtime names, and their enabled status would all be available to the handler for such an operation.

I generally don't like adding lots of server-side operations that are just convenience ops for things the client could do. That leads to a cluttered API and might make it harder to evolve the server later without breaking compatibility. But in this case we may have to, since it seems this isn't something the client really can't do in a reasonable manner.

> The deployment-overlay command fails to redeploy affected deployments
> ---------------------------------------------------------------------
>
>                 Key: WFCORE-1752
>                 URL: https://issues.jboss.org/browse/WFCORE-1752
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 3.0.0.Alpha5
>            Reporter: ehsavoie Hugonnet
>            Assignee: Jean-Francois Denise
>
> The deployment-overlay command fails to redeploy affected deployments if the runtime-name isn't the same as the deployment name. Since affected deployment to be redeployed should be running the couple runtime-name + enabled == true should be used to define which deployments are affected instead of using the deployment name since the name used in overlay is the runtime-name



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)