-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Reporting/New Platform Migration] Use a new config service on server-side (re-do) #61696
[Reporting/New Platform Migration] Use a new config service on server-side (re-do) #61696
Conversation
…ation-server-config
…ation-server-config
…ation-server-config
Goal here is to re-run the full CI process a few times. |
@elasticmachine merge upstream |
1 similar comment
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
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.
Some NITs from the Telemetry end :)
@@ -11,16 +11,17 @@ import { PluginStart as DataPluginStart } from '../../../../../src/plugins/data/ | |||
import { SecurityPluginSetup } from '../../../../plugins/security/server'; | |||
import { XPackMainPlugin } from '../../xpack_main/server/xpack_main'; | |||
import { ReportingPluginSpecOptions } from '../types'; | |||
import { ReportingConfig, ReportingConfigType } from './core'; | |||
|
|||
export interface ReportingSetupDeps { | |||
elasticsearch: ElasticsearchServiceSetup; | |||
security: SecurityPluginSetup; | |||
usageCollection: UsageCollectionSetup; |
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.
In the kibana.json
, usageCollection
is an "optionalDependency"
, which is the way to go.
ReportingSetupDeps
should define it as an optional dependency.
exportTypesRegistry, | ||
collectionIsReady | ||
); | ||
usageCollection.registerCollector(collector); | ||
plugins.usageCollection.registerCollector(collector); |
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.
plugins.usageCollection
might be undefined
@@ -93,51 +90,6 @@ export type ReportingResponseToolkit = Legacy.ResponseToolkit; | |||
|
|||
export type ESCallCluster = CallCluster; |
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.
Type-wise it should be the same and there shouldn't be any issues but CallCluster
is now APICaller
in NP from 'src/core/server'
Replaced with #62500 |
Summary
Re-introduces the reporting config change that was reverted mid-week: #61075
Original PR: #55882.
This PR has successfully undergone the flaky-test runner: https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/312/testReport/