-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[uiActions] notify feature usage #72019
Comments
@elastic/kibana-platform, @kobelb, When creating this issue I didn't realise this is a server side only api. URL Drilldown will be based on Please advice if we should we skip this |
When implementing the feature usage API, the only consumers we had at this point were supposed to be server-side, which is why we did not add a similar API on the client. @kobelb what should we do here? |
Unfortunately, I think we'll have to add a client-side API to enable situations like these... @pgayvallet do you mind creating an issue to do so? When we first implemented these APIs, I was expecting us to have server-side enforcement of all licensed features because relying solely on the client-side enforcement seemed easy to evade by directly hitting Kibana APIs. However, for situations like URL Drilldowns, I can envision an architecture where there isn't the case and it'd be convoluted to try and force this constraint. |
Created #72572. I guess we ideally want this to be done during 7.10? |
We will work on URL drilldown during 7.10 and plan it gets into that train |
Pinging @elastic/kibana-app-arch (Team:AppArch) |
In #68507 we added basic licensing support for dynamic ui actions and drilldowns.
This isn't actually used yet, but will be used for Url drilldown.
We should extend current licensing support in ui actions to notify about feature usage:
It should be noted that we're only concerned with when a feature is actually used, not when we perform a licensing check to determine whether or not to show or hide a specific feature.
Part of #71854
The text was updated successfully, but these errors were encountered: