]
Brian Stansberry moved WFLY-4177 to WFCORE-462:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-462 (was: WFLY-4177)
Affects Version/s: 1.0.0.Alpha14
(was: 9.0.0.Alpha1)
Component/s: CLI
(was: CLI)
Fix Version/s: (was: No Release)
Deployment info should not accept wildcard as server-group parameter
--------------------------------------------------------------------
Key: WFCORE-462
URL:
https://issues.jboss.org/browse/WFCORE-462
Project: WildFly Core
Issue Type: Enhancement
Components: CLI
Affects Versions: 1.0.0.Alpha14
Environment: All environments.
Reporter: Filippe Spolti
Assignee: Filippe Spolti
Priority: Optional
Labels: core
Original Estimate: 2 days
Remaining Estimate: 2 days
Actually the deployment-info in a domain mode accepts the wildcard *, but when the * is
given the CLI lists only the last server-group in the list, not all. The help says:
- single server group with a state report about each deployment in the
domain with regard to the selected server group.
In this case, the --server-group argument is required and its value
must be a specific server group name, not a wildcard expression.
The output of the command is a table with headers NAME, RUNTIME-NAME and STATE.
Ex:
[domain@localhost:9990 /] deployment-info --name=test.war --server-group=*
NAME RUNTIME-NAME STATE
test.war test.war not added
After the change:
[domain@localhost:9990 /] deployment-info --name=test.war --server-group=*
Wildcards are note permited here, please give a valid server-group name.