-
Notifications
You must be signed in to change notification settings - Fork 18
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the change. Please make sure commits are squashed before merging.
kibana.json
Outdated
"kibanaVersion": "7.9.1", | ||
"configPath": ["opendistro_anomaly_detection_kibana"], | ||
"requiredPlugins": ["navigation"], | ||
"optionalPlugins": ["opendistro-alerting", "opendistro_alerting"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why add two alerting plugins?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was the naming conventions for the ES and Kibana alerting plugins. With the new naming conventions for the Kibana plugin this will need to be revisited, I'll make a note of it. Also, adding optional plugins doesn't really have much functionality at all, and we could remove altogether. See here
Issue #, if available:
Description of changes:
This PR migrates the entire plugin to the new Kibana platform, which is required for Kibana 7.10. A follow up PR will be made to upgrade the plugin to 7.10. Overview of the changes can be found here.
The main changes include:
index
andplugin
files for eachkibana.json
manifest fileIHttpService
to Kibana's coreHttpSetup
client, and changing all request/response parsing logic accordinglyIClusterClient
with all of the services, and changing the different route functions to be grouped into different service classesui/*
statements, and accessing core services (chrome breadcrumbs, toast notifications, etc.) by consuming them via React contextNotes:
yarn start
in the plugin repo anymore - need to run in base Kibana dirKnown issues:
yarn build
issues - the built artifact won't work with the binary Kibana. This is fixed separately, will be included in a follow up PRTask backlog:
yarn
command changesBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.