[New Platform] APIs needed for opening a connection to the Kibana server

[tsullivan]

Kibana Reporting plugin opens a headless browser to navigate / authenticate with the running Kibana web server to display visualizations for screenshot capture.

In order for the connection to establish, the plugin needs to form a complete URL of the kibana web service, using:

• server protocol (http or https)
• server host
• server port

Reporting also tags the queued jobs with metadata about the running instance:

• server name
• server uuid

Also, the path.data config needs to be available to Reporting plugin somehow.

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[tsullivan]

server uuid

I found where this is available from coreSetup.uuid.getInstanceUuid. Thanks! :)

[tsullivan]

Added a note to the description about the need for path.data

[pgayvallet]

path.data is already available on PluginInitializerContext

    const legacyConfig = await this.initializerContext.config.legacy.globalConfig$
      .pipe(take(1))
      .toPromise();
    const dataPath = legacyConfig.path.data

this is a temporary solution, but will not be removed until we expose it in another way, and therefor should be used if you need to.

[pgayvallet]

@restrry Does an API from httpSetup like getServerInfo returning a subset of the http config values would make sense to you?

getServerInfo() => { host: string, name: string, port: string, others? }

Also do you know where to retrieve the protocol (http or https) from the http config? I don't see it directly mentioned in src/core/server/http/http_config.ts. Can it be deduced from ssl.enabled ?

[mshustov]

@pgayvallet we can get this information from hapiServer.info https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/hapi/v17/index.d.ts#L2571-L2619

[tsullivan]

Hi, it looks like I should open a separate issue for path.data.

Filed: #56760