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.

Current Situation

Currently, it is possible to deploy applications using:

deploy C:\path\to\application.jar --name=... --runtime-name=...

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_

deploy C:\path\to\application.jar --name=app_A.jar --runtime-name=app_A-1.jar

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.

Request

When deploying applications, we could provide an additional argument, called description. It would allow us to do the following:

deploy C:\path\to\application-1.0.0.jar --name=application-1.jar --description="Application v1.0.0"

When doing /deployment=application-1.jar:read-resource, it would result in the following output:

{                                                          
    "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                           
    }                                                      
}                                                          

This description information should be kept when replacing that particular deployment, so when doing:

deploy C:\path\to\application-1.0.0.jar --name=application-1.jar --force

it should replace the existing application, but without deleting the description information. That should be removed when doing:

/deployment=application-1.jar:remove

When explicitly adding the description argument to the deploy command, the description has to be replaced by the new one.