-
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
Legacy ES plugin pre-removal cleanup #75779
Legacy ES plugin pre-removal cleanup #75779
Conversation
…-plugin-pre-removal
Pinging @elastic/kibana-platform (Team:Platform) |
|
||
export default function (kibana) { | ||
let defaultVars; | ||
|
||
return new kibana.Plugin({ | ||
require: ['kibana'], | ||
require: [], |
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.
Wouldn't it affect an execution order?
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.
Yea, the kibana
legacy plugin is no longer assured to be initialized before the es
one. However as the kibana plugin is an empty shell now, this shouldn't have any consequences (and is preparing the actual removal of the kibana
plugin)
@@ -523,6 +523,4 @@ export interface CallCluster { | |||
export interface ElasticsearchPlugin { | |||
status: { on: (status: string, cb: () => void) => void }; | |||
getCluster(name: string): Cluster; | |||
createCluster(name: string, config: ClusterConfig): Cluster; | |||
waitUntilReady(): Promise<void>; |
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.
let's remove this comment as well
* waitUntilReady() waits for the kibana index to exist and then for the |
retest |
💚 Build SucceededBuild metricsoss distributable file count
distributable file count
History
To update your PR or re-run it, just comment with: |
* delete integration tests * remove legacy version healthcheck / waitUntilReady * remove handleESError * remove createCluster * no longer depends on kibana plugin * fix kbn_server * remove deprecated comment and dead code * revert code removal, apparently was used (?) * Revert "revert code removal, apparently was used (?)" This reverts commit 6948185 # Conflicts: # src/legacy/core_plugins/elasticsearch/index.js # src/legacy/core_plugins/elasticsearch/lib/__tests__/handle_es_error.js # src/legacy/core_plugins/elasticsearch/lib/handle_es_error.js
* delete integration tests * remove legacy version healthcheck / waitUntilReady * remove handleESError * remove createCluster * no longer depends on kibana plugin * fix kbn_server * remove deprecated comment and dead code * revert code removal, apparently was used (?) * Revert "revert code removal, apparently was used (?)" This reverts commit 6948185 # Conflicts: # src/legacy/core_plugins/elasticsearch/index.js # src/legacy/core_plugins/elasticsearch/lib/__tests__/handle_es_error.js # src/legacy/core_plugins/elasticsearch/lib/handle_es_error.js
Summary
Related to #71927
Remove all the dead parts of the legacy ES plugin, only keeping the 'proxy' / endpoints that are still used until #73993 and #73992 are addressed.