[Console] Remove unused function#159041
Conversation
c273f62 to
012422b
Compare
💛 Build succeeded, but was flaky
Failed CI StepsTest FailuresMetrics [docs]Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
|
Pinging @elastic/platform-deployment-management (Team:Deployment Management) |
sabarasaba
left a comment
There was a problem hiding this comment.
Changes lgtm! Do we have to ping anyone about this possible breaking change for external plugins or just with the label is enough?
|
Thanks a lot for your review, @sabarasaba! |
|
Cool! Was just wondering if anyone within elastic has to be notified about it (support?) but if the label works then should be all good! |
## Summary Related to #159041 While working on #161684, I noticed another unused function. There is no usage in the code base of the "extensions" function and I think it would be better to delete it from Console. That makes the remaining code that we need to work with easier to understand. ### Release note The function `addExtensionSpecFilePath` is removed from the Console plugin setup contract (server side).
Summary
While working on #159410, I noticed that there are some unused functions in the Console server side plugin contracts. This PR removes the function
addProcessorDefinitionfrom thestartcontract. I was not able to find any uses of this function in the Kibana code. I believe it might have been planned to be used for ingest processors but currently we use the_processorendpoint for that (see here). And since the tests also pass I think it's safe to remove this function. I'm using the labelrelease_note:breakingbecause the plugin's contracts are public and theoretically it's possible that there are some external plugins that use that function.Release note
The function
addProcessorDefinitionis removed from the Console plugin start contract (server side).