mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-28 17:34:17 -04:00
Add purge option to remove plugin CLI
By default, the remove plugin CLI command preserves configuration files. This is so that if a user is upgrading the plugin (which is done by first removing the old version and then installing the new version) they do not lose their configuration file. Yet, there are circumstances where preserving the configuration file is not desired. This commit adds a purge option to the remove plugin CLI command. Relates #24981
This commit is contained in:
parent
8f8fc74b2e
commit
9b4a189147
7 changed files with 200 additions and 87 deletions
|
@ -107,7 +107,14 @@ Plugins can be removed manually, by deleting the appropriate directory under
|
|||
sudo bin/elasticsearch-plugin remove [pluginname]
|
||||
-----------------------------------
|
||||
|
||||
After a Java plugin has been removed, you will need to restart the node to complete the removal process.
|
||||
After a Java plugin has been removed, you will need to restart the node to
|
||||
complete the removal process.
|
||||
|
||||
By default, plugin configuration files (if any) are preserved on disk; this is
|
||||
so that configuration is not lost while upgrading a plugin. If you wish to
|
||||
purge the configuration files while removing a plugin, use `-p` or `--purge`.
|
||||
This can option can be used after a plugin is removed to remove any lingering
|
||||
configuration files.
|
||||
|
||||
[float]
|
||||
=== Updating plugins
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue