Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add plugin version check to Kibana startup #6652

Closed
simianhacker opened this issue Mar 24, 2016 · 1 comment · Fixed by #8283
Closed

Add plugin version check to Kibana startup #6652

simianhacker opened this issue Mar 24, 2016 · 1 comment · Fixed by #8283

Comments

@simianhacker
Copy link
Member

simianhacker commented Mar 24, 2016

The nature of this issue has changed. See here for updated description


See discussion of pros and cons #6532

@epixa epixa added the blocker label May 18, 2016
@BigFunger BigFunger changed the title Enforce Plugin Version Compatibility at Patch Level Version Add plugin version check to Kibana startup Sep 12, 2016
@BigFunger
Copy link
Contributor

Currently the plugin installer does a version check to make sure that the plugin being installed is compatible with the installation of Kibana.

After #8222, this will include functionality that allows the plugin author to explicitly specify which version of Kibana the plugin is compatible with regardless of the plugin version.

The problem is that if the user successfully installs plugins (with the version check passing) and then updates to a new version of Kibana, they have successfully put Kibana in a state where there are incompatible plugins installed.

To fix this, we need to add a check during the start-up process of kibana while plugins are being initialized that checks to see if the plugin's Kibana version still matches the currently installed Kibana version. If it does not, the following should happen:

  1. The user should be presented with a warning message in the console.
  2. The plugin should be disabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants