-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Kibana 7.6: plugin installation fails #59543
Comments
Pinging @elastic/kibana-operations (Team:Operations) |
@fbaligand looks like the issue is that you've |
What do you think we should do here? This is clearly a usability issue, maybe we should just have a better error message? Maybe validate that the cwd includes the |
Hi, Thanks for your answer @spalger ! That said, in previous Kibana releases (7.5 and previous), we can install a kibana plugin directly from bin directory. |
By the way, it does not work also, if we are in another directory. And this worked perfectly in previous releases. |
Yeah, okay, since this worked in previous versions I'll go ahead and track down the issue to make sure that it continues to work in the next version. Sorry for the break! |
Thank you very much @spalger ! |
Kibana version:
7.6.0 and 7.6.1
Server OS version:
Windows 10 ans Linux RHEL 7
Original install method (e.g. download page, yum, from source, etc.):
download page
Describe the bug:
When I install a community plugin, I get the following error:
Plugin installation was unsuccessful due to error "Cannot delete files/directories outside the current working directory. Can be overridden with the
forceoption."
I don't reproduce the issue on Kibana 7.5.x
Steps to reproduce:
./kibana-plugin install https://github.com/fbaligand/kibana-enhanced-table/releases/download/v1.8.0/enhanced-table-1.8.0_7.6.1.zip
And plugin is not installed in "plugins" directory
Expected behavior:
Plugin installed correctly
Any additional context:
Discussion in slack: https://app.slack.com/client/TNLBGCXTQ/CRTSV34RK/thread/CRTSV34RK-1583478396.003800
The text was updated successfully, but these errors were encountered: