[jboss-jira] [JBoss JIRA] Updated: (AS7-713) Persist named rollout plans for reuse by clients

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated AS7-713:
---------------------------------

        Summary: Persist named rollout plans for reuse by clients  (was: Persist named deployment groups for reuse by clients)
    Description: 
It seems to me that we will have multiple clients using the management api to deploy to domain and they all today need to somehow define at every deployment the rollout plan to use if not just the hardwired default.

To avoid having to redefine that everytime it means clients such as IDE's, management console, command line tools will all have to somehow be able to persist this information in their own local setup and these will probably all be a little bit different and thus not shareable.

Thus I suggest that it should be possible to define named rollout plan settings that all the clients can query and provide as named arguments in the managed deployments instead of it being up to every client to define it.


  was:
It seems to me that we will have multiple clients using the management api to deploy to domain and they all today need to somehow define at every deployment the deployment plan to use if not just the hardwired default.

To avoid having to redefine that everytime it means clients such as IDE's, management console, command line tools will all have to somehow be able to persist this information in their own local setup and these will probably all be a little bit different and thus not shareable.

Thus I suggest that it should be possible to define named deployment settings that all the clients can query and provide as named arguments in the managed deployments instead of it being up to every client to define it.




Modified title and description to use "rollout plan" instead of "deployment".  These settings can apply to any update, not just deployments, so I've been using "rollout plan" to avoid ambiguity.

> Persist named rollout plans for reuse by clients
> ------------------------------------------------
>
>                 Key: AS7-713
>                 URL: https://issues.jboss.org/browse/AS7-713
>             Project: Application Server 7
>          Issue Type: Feature Request
>            Reporter: Max Rydahl Andersen
>            Assignee: Jason Greene
>
> It seems to me that we will have multiple clients using the management api to deploy to domain and they all today need to somehow define at every deployment the rollout plan to use if not just the hardwired default.
> To avoid having to redefine that everytime it means clients such as IDE's, management console, command line tools will all have to somehow be able to persist this information in their own local setup and these will probably all be a little bit different and thus not shareable.
> Thus I suggest that it should be possible to define named rollout plan settings that all the clients can query and provide as named arguments in the managed deployments instead of it being up to every client to define it.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira