Skip to content
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

[New Platform] API needed for referencing the path.data value from config #56760

Closed
tsullivan opened this issue Feb 4, 2020 · 2 comments
Closed
Labels
enhancement New value added to drive a business result Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@tsullivan
Copy link
Member

Describe the feature:

In order for plugins to know where to write data to the filesystem as needed, the plugin needs to know the value of the path.data config setting. This value needs to be exposed in the Kibana New Platform somehow.

Describe a specific use case for the feature:
Reporting plugin will use path.data to extract the headless browser executable at start time.

@tsullivan tsullivan added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:New Platform enhancement New value added to drive a business result labels Feb 4, 2020
@elasticmachine
Copy link
Contributor

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

@joshdover
Copy link
Contributor

joshdover commented Feb 4, 2020

This already exists:

class MyPlugin {
  constructor(initContext: PluginInitializerContext) {
    // Creates an observable for just the path.data config
    this.pathData$ = initContext.config.legacy.globalConfig$.pipe(
      map(c => c.path.data)
    );
  }
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

3 participants