Open acchen97 opened 8 years ago
In my opinion the most important thing to provide here is idempotent updates command, and this will be hard to archive only with a ---version
flag, obviously this should be be skip as is a good feature to have for the update command. I some challenges here:
---version
flag, due to possible inter plugin conflicts. Some of this might be archived by sharing the install status (aka Gemfile.lock
file).what do you think?
@purbon I agree idempotent updates are important and I think the --version flag should solve it if we resolve the conflicts within the update operation (update or uninstall dependent plugins).
The current way to install a specific version of a plugin is to uninstall all plugins that depend on it first, then uninstall the actual plugin and reinstall it with "install --version".
Uninstall command user feedback is another item, success and failure (+reasons why) should be clearly displayed and I'm +1 on more feedback here.
Let's give an example to this request:
Scenario:
According to https://github.com/logstash-plugins/logstash-output-kafka we should use plugin version 4.0.0 to use the correct plugin version to work with Kafka 0.9 brokers.
-> How do I install this version 4.0.0 on the cli?
bin/logstash-plugin install logstash-output-kafka --version 4.0.0
does not work.
Right now I somehow have to do this manually, wasting some precious time on how to automate/script this.
@ppuschmann I have the same use case and trying to make it working. Can you please guide me what manual step you have done?
any solution here?
@wongchao the current workaround here is to uninstall and reinstall with the desired plugin version.
@raiusa I have no workaround. We "fixed" this by installing a newer version of Logstash that already shipped with a plugin that is (more) compatible to our kafka-broker version.
There are use cases where a user may need to update a plugin to a particular version that isn't the latest. There should be a --version flag for "bin/plugin update" to enable this.
More context here: https://github.com/elastic/logstash/issues/3334