[
https://issues.jboss.org/browse/WFCORE-1809?page=com.atlassian.jira.plugi...
]
Alexey Loubyansky commented on WFCORE-1809:
-------------------------------------------
Could be. Let's consider a few cases though.
Suppose, I have multiple custom config directories. I launch a server using one of those
custom configs. Then I apply a patch. The patching mechanism will backup the config
directory.
Question: which one? The active one? All of them? The patching mechanism is not aware of
all the possible custom config locations.
What if I then launch a server using another config? The server will actually be patched
for that config too.
Question: what if I now rollback that last patch? Which config dir should I reset? The
active one? All of them? Again, custom config locations are not known.
Suppose we have a server with some patching history. I create a custom config dir, launch
the server and rollback a few patches
Question: which config dirs should be reset?
JBoss CLI patch command doesn't honor custom configuration
location
-------------------------------------------------------------------
Key: WFCORE-1809
URL:
https://issues.jboss.org/browse/WFCORE-1809
Project: WildFly Core
Issue Type: Bug
Components: Patching
Affects Versions: 3.0.0.Alpha8
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Suppose we are using custom standalone directory(example: standalone_dev) and if we try
to rollback applied CP patch, with "--rest-configuration=true" option, it always
restore configuration files from default location(JBOSS_HOME/standalone) not from the
"standalone_dev" directory. I can see same result when I try to rollback patch
through management console and through JBoss CLI in connected mode.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)