-
Enhancement
-
Resolution: Done
-
Minor
-
None
-
None
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
- blocks
-
WFCORE-695 OutOfMemoryErrors when adding large deployment in CLI batch with audit logging enabled
- Resolved
- clones
-
JBEAP-7477 Unify deployment operations
- Closed
- is related to
-
WFCORE-3649 'deploy' command mandates use of --replace but fails with "Unrecognized arguments: [--replace]"
- Resolved
-
WFCORE-3648 Options --disabled/--enabled/--replace are missing in CLI code completion
- Resolved
- relates to
-
WFCORE-3578 Tests for unified deployment operations
- Resolved