[jboss-jira] [JBoss JIRA] (WFCORE-339) Provide a way to add a description for a deployment

[Brian Stansberry (JIRA)]

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

Brian Stansberry moved WFLY-1164 to WFCORE-339:
-----------------------------------------------

        Project: WildFly Core  (was: WildFly)
            Key: WFCORE-339  (was: WFLY-1164)
    Component/s: Domain Management
                     (was: Domain Management)


> Provide a way to add a description for a deployment
> ---------------------------------------------------
>
>                 Key: WFCORE-339
>                 URL: https://issues.jboss.org/browse/WFCORE-339
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Sven Plath
>            Priority: Minor
>
> h2.Summary
> It would be nice to have a feature that allows to add an *optional description* to a deployment when using the console or the web interface to deploy it.
> h2.Current Situation
> Currently, it is possible to deploy applications using:
> {code}
> deploy C:\path\to\application.jar --name=... --runtime-name=...
> {code}
> The _runtime-name_ is used for dependency resolution. When for example we have an application *app_A-1.0.0.jar* and deploy it using the following command_
> {code}
> deploy C:\path\to\application.jar --name=app_A.jar --runtime-name=app_A-1.jar
> {code}
> we loose the version information of that application.
> * We could write the version into the _name_ argument, however it could lead to multiple deployments of the same application when the old one is not removed before updating.
> * We could add the version information into the _runtime-name_ argument, but that would be problematic when updating applications to a newer version. We would have to change the deployment-descriptor.
> h2.Request
> When deploying applications, we could provide an additional argument, called *description*. It would allow us to do the following:
> {code}
> deploy C:\path\to\application-1.0.0.jar --name=application-1.jar --description="Application v1.0.0"
> {code}
> When doing _/deployment=application-1.jar:read-resource_, it would result in the following output:
> {code}
> {                                                          
>     "outcome" => "success",                                
>     "result" => {                                          
>         "content" => [{"hash" => bytes {                   
>             0x10, 0xd6, 0x20, 0x46, 0x74, 0xcc, 0xe5, 0x39,
>             0x7d, 0xef, 0x2e, 0xe3, 0x26, 0x45, 0x28, 0xad,
>             0xa5, 0xde, 0xdd, 0x80                         
>         }}],                                               
>         "enabled" => true,                                 
>         "name" => "application-1.jar",                  
>         "persistent" => true,                              
>         "runtime-name" => "application-1.jar",          
>         "description" => "Application v1.0.0",
>         "subdeployment" => undefined,                      
>         "subsystem" => undefined                           
>     }                                                      
> }                                                          
> {code}
> This description information should be kept when replacing that particular deployment, so when doing:
> {code}
> deploy C:\path\to\application-1.0.0.jar --name=application-1.jar --force
> {code}
> it should replace the existing application, but without deleting the description information. That should be removed when doing:
> {code}
> /deployment=application-1.jar:remove
> {code}
> When explicitly adding the _description_ argument to the _deploy_ command, the description has to be replaced by the new one.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)