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

expose public licensing APIs from core #191771

Closed
TinaHeiligers opened this issue Aug 29, 2024 · 3 comments
Closed

expose public licensing APIs from core #191771

TinaHeiligers opened this issue Aug 29, 2024 · 3 comments
Labels
discuss Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@TinaHeiligers
Copy link
Contributor

TinaHeiligers commented Aug 29, 2024

Alternative implementation toward #187296.
Given that we cannot move the entire licensing plugin to core, we should consider if exposing frequently used licensing APIs from core, similarily to how authc and audit is exposed from core.security. We would need to delegate the implementation back to the licensing plugin.

cc @SiddharthMantri

@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 29, 2024
@SiddharthMantri SiddharthMantri self-assigned this Aug 30, 2024
@jughosta jughosta added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Sep 2, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Sep 2, 2024
@TinaHeiligers TinaHeiligers added the Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! label Sep 3, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

@SiddharthMantri SiddharthMantri removed their assignment Sep 5, 2024
@TinaHeiligers
Copy link
Contributor Author

There isn't a benefit to exposing licensing APIs from core without moving the implementation. We cannot cross the code licensing border and will revisit if and when that changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Development

No branches or pull requests

4 participants