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

Client-side implementation of licensed feature usage API #72572

Closed
pgayvallet opened this issue Jul 21, 2020 · 1 comment · Fixed by #75486
Closed

Client-side implementation of licensed feature usage API #72572

pgayvallet opened this issue Jul 21, 2020 · 1 comment · Fixed by #75486
Assignees
Labels
enhancement New value added to drive a business result Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@pgayvallet
Copy link
Contributor

pgayvallet commented Jul 21, 2020

In #60984 (implem in #63549) we implemented the LFU API on the server-side only, as it was sufficient for the initial consumers of the API.

However it is no longer the cases, and needs such as #72019 (comment) requires the same API exposed on the client-side.

We need to add a similar LFU API for client-side consumers.

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

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

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 Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants