Release Notes - Petals ESB CLI - Version 2.2.0 - HTML format

Bug

• [PETALSESBCLI-82] - Error 'do_stop_all_containers: not found' restarting petals-cli-nagios
• [PETALSESBCLI-86] - Arguments proposed by the completer of the command 'undeploy' on option '-a' are invalid
• [PETALSESBCLI-87] - Unable to deploy a local artifact on a remote container
• [PETALSESBCLI-88] - java.lang.ArrayIndexOutOfBoundsException when operand flag is misplaced
• [PETALSESBCLI-91] - Unable to execute system command with arguments
• [PETALSESBCLI-95] - Invalid content assistance on the passphrase of 'topology-list'
• [PETALSESBCLI-96] - The topology tree displayed by 'topology-list' has no indent for sub-domain level
• [PETALSESBCLI-101] - NullPointerException when trying to complete the command 'monitoring'
• [PETALSESBCLI-102] - Unable to deploy a component having no installer configuration MBean
• [PETALSESBCLI-106] - Improper output returned by command 'list'
• [PETALSESBCLI-110] - Uncorrect information returns by the command 'show' for shared libraries
• [PETALSESBCLI-121] - The host name of a container returned by 'topology-list' must prefixed by '***'

Improvement Request

• [PETALSESBCLI-53] - The auto-completion of artifact name should propose only valid artifact names
• [PETALSESBCLI-79] - The command 'help' requires a connection
• [PETALSESBCLI-81] - Use the hostname instead of the IP address in the prompt of Petals CLI console
• [PETALSESBCLI-83] - The command 'registry-sync' must be moved as an extension
• [PETALSESBCLI-85] - Introduce the command 'move-container'
• [PETALSESBCLI-89] - All deployed artifacts should be undeployable in one shoot with the command 'undeploy'
• [PETALSESBCLI-90] - Petals CLI should be able to get environment variable values
• [PETALSESBCLI-94] - The command 'topology-list' should be improved to support a container filter
• [PETALSESBCLI-97] - The output of 'registry-list' should be controllable
• [PETALSESBCLI-98] - The command 'registry-list' should be improved to support a container filter
• [PETALSESBCLI-99] - Deployable service unit deployment/undeployment
• [PETALSESBCLI-104] - Add the version of shared library in output of command 'list'
• [PETALSESBCLI-105] - Improve the command 'list' to filter shared libraries on a given version
• [PETALSESBCLI-109] - The command 'show' is not clear when used to get information about a given version of a shared library
• [PETALSESBCLI-111] - On command 'show', the artifact type should need a dedicated option
• [PETALSESBCLI-112] - On command 'start-artifact', the artifact type should need a dedicated option
• [PETALSESBCLI-113] - On command 'stop-artifact', the artifact type should need a dedicated option
• [PETALSESBCLI-114] - On command 'undeploy', the artifact type should need a dedicated option
• [PETALSESBCLI-115] - The command 'undeploy' is not clear when used to undeploy a given version of a shared library
• [PETALSESBCLI-117] - The default value of the HTTP port should be one of the available free ports
• [PETALSESBCLI-119] - Petals ESB CLI requires a Java Runtime Environment head less
• [PETALSESBCLI-120] - Add a flag to not automatic start the artifact during deploiement
• [PETALSESBCLI-122] - The command 'topology-list' should return container states
• [PETALSESBCLI-123] - Create a new command to reload the property file of a JBI component

Task

• [PETALSESBCLI-80] - Few unit tests fail when executed through Sonar
• [PETALSESBCLI-84] - Take into account: the JMX API 'PetalsAdminService.retrieveTopology' moved to 'TopologyService.retrieveTopology'
• [PETALSESBCLI-103] - Explode Petals ESB CLI in two parts

The text area below allows the project release notes to be edited and copied to another document.