]
Jean-Francois Denise moved JBEAP-12945 to WFCORE-3223:
------------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-3223 (was: JBEAP-12945)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: CLI
(was: CLI)
(was: User Experience)
(was: Web Console)
Affects Version/s: (was: 7.1.0.DR8)
Unify deployment operations
---------------------------
Key: WFCORE-3223
URL:
https://issues.jboss.org/browse/WFCORE-3223
Project: WildFly Core
Issue Type: Enhancement
Components: CLI
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
Priority: Minor
*Now*
* Webconsole provides clear set of operations over deployment (disable, replace, remove,
...). It is clear always how to use them and where they are.
* In CLI, the same operations can be called in different ways and some of them have
different names in comparsion to webconsole.
*Problem*
* CLI deployment commands has lack of unified approach.
Examples
* Webconsole command: Disable
** undeploy --name=my-deployment --keep-content
* Replace
** deploy --force /.../jboss-ejb-in-war.war --name=my-deployment.war
--runtime-name=my-deployment.war
* Remove
** undeploy --name=my-deployment
* Explode
** /deployment=my-deployment.war:explode()
* Browse content
** /deployment=my-deployment.war:browse-content()
*Proposed solution*
1. Unify vocabulary, check following words at least:
* disable vs. keep-content
* replace vs. force
2. Provide CLI commands for explode and browse content as well, for example.
* deployment-explode --name=my-deployment
* deployment-browse-content --name=my-deployment