-
Bug
-
Resolution: Done
-
Critical
-
None
The patch command is still available under a standalone context, however, it should be completely disabled since its usage makes no sense in a standalone.
So far we have removed the patch command group, e.g. "pat+<TAB>" no longer completes to "patch" and the command used without arguments returns as no available:
[standalone@localhost:9990 /] patch The command is not available in the current context. [disconnected /] patch The command is not available in the current context.
However, when using a subcommand in a disconnected session, it is still "functional":
[disconnected /] patch info Version: 30.0.0.Final-SNAPSHOT Cumulative patch ID: base One-off patches: none
In a connected interactive session it returns an error since the /core-service/patching resource was also removed:
[standalone@localhost:9990 /] patch info WFLYCTL0030: No resource definition is registered for address [("core-service" => "patching")]
In addition, the "help patch" should also be removed from standalone mode.
The "patch" command should be only functional in Domain Mode since it still needs to be used to patch secondary hosts running on legacy versions from a Domain Controller
- clones
-
JBEAP-25791 Patch high level command should be completely disabled in standalone mode
- Closed