Remove data_enhanced plugin#122075
Conversation
|
@elasticmachine merge upstream |
1d61349 to
83640bc
Compare
|
@elasticmachine merge upstream |
| } | ||
| } | ||
| }, | ||
| "search-session": { |
There was a problem hiding this comment.
@elastic/telemetry this config was moved from x-pack to oss. Is it safe to do? Is there anything else to be aware of?
There was a problem hiding this comment.
yup! all good! I don't think it changes the resulting output :)
| "include": [ | ||
| "src/core/server/index.ts", | ||
| "src/core/public/index.ts", | ||
| "src/plugins/data/server/index.ts", |
There was a problem hiding this comment.
After moving the code from data_enhanced to data this type generation for docs stopped working because data now references code from x-pack (task_manager, security) and this changed the output folder structure of this types.
Since we don't use these types for app services plugins generation anymore, I just removed them. I added the rootDir to preserve the previous file tree output structure.
| renameFromRoot('kibana.autocompleteTimeout', 'data.autocomplete.valueSuggestions.timeout', { | ||
| level: 'warning', | ||
| }), | ||
| renameFromRoot('xpack.data_enhanced.search.sessions', 'data.search.sessions', { |
There was a problem hiding this comment.
session config has to be changed
- @Dosant to allowlist in cloud
|
@elasticmachine merge upstream |
lukasolson
left a comment
There was a problem hiding this comment.
Code changes LGTM and things seem to be working properly (even having sessions from master & then checking out this PR).
| checkPersistedCompletedSessionExpiration | ||
| ); | ||
|
|
||
| this.setupCompleted = true; |
There was a problem hiding this comment.
I'm not sure I understand why this is now necessary. Could you explain?
There was a problem hiding this comment.
Mostly a precaution, because task_manager plugin is optional, we have to handle a code branch where search_service doesn't have access to task_manager and it can't initialize session_service:
kibana/src/plugins/data/server/search/search_service.ts
Lines 159 to 165 in 1bdbafe
This makes it possible so that setup is never called and I wanted a clear error in case start is called by mistake in this case
| data: DataPublicPluginStart; | ||
| } | ||
| // eslint-disable-next-line @typescript-eslint/no-empty-interface | ||
| export interface StartPlugins {} |
YulNaumenko
left a comment
There was a problem hiding this comment.
Security Solution changes LGTM
…/kibana into d/2021-12-22-remove-data-enhanced
| } | ||
| } | ||
| }, | ||
| "search-session": { |
There was a problem hiding this comment.
yup! all good! I don't think it changes the resulting output :)
|
@elasticmachine merge upstream |
|
Pinging @elastic/kibana-app-services (Team:AppServicesSv) |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
💛 Build succeeded, but was flakyMetrics [docs]Module Count
Public APIs missing comments
Async chunks
Public APIs missing exports
Page load bundle
Unknown metric groupsAPI count
async chunk count
ESLint disabled line counts
References to deprecated APIs
Total ESLint disabled count
Unreferenced deprecated APIs
History
To update your PR or re-run it, just comment with: |
Code moved into `data` plugin
Summary
Close #119321
This pr removes the
data_enhancedplugin and moves its code to thedatapluginThe
_enhancedplugins were created as a license workaround which is no longer needed and we can clean it up.Most of the moved code is search-sessions code. That code moved to
dataplugin anddataplugin now has to depend onsecurityandtask_manager(src plugins can depend on x-pack plugins as an optional dep). In some places this dependency created circular dependencies which were fixed by fixing the dependence to be ondataViewsplugin instead ofdataplugin.Risk Matrix
For maintainers
Release notes
xpack.data_enhanced.*kibana.yml config params are deprecated anddata.*counterparts should be used instead