-
Notifications
You must be signed in to change notification settings - Fork 456
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
fleet-server package #524
Comments
@aleksmaus @nchaulet Here the issue to track the package for the fleet-server. I assigned @aleksmaus to it as I think he already built a package in the past. Happy to help with this one. I listed a few questions above we should also discuss first, I'm sure there are more, please add them to the list. |
Pinging @elastic/ingest-management (Team:Ingest Management) |
@ruflin I haven't build the kibana package that boostraps the indices before yet. |
@aleksmaus Sorry, I thought you built the one for osquery. A good starting point is here https://github.com/elastic/integrations/blob/master/CONTRIBUTING.md#tips-for-building-integrations and look at some of the existing packages. We should not allow users to uninstall the package, we do the same for endpoint for example. |
I did, but it doesn't bootstrap any indices. Will dig. |
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as |
For fleet-server to work properly, quite a few assets need to be loaded in advance. Currently the setup is done by
fleet-server
itself but instead it should be done by Kibana. As the assets to be installed are mainly templates this can be done with a package to not have to duplicate the logic.This issue is to discuss details around the package and track the implementation.
Few thoughts around the package:
The text was updated successfully, but these errors were encountered: