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

Review 1 or more of Core's existing APIs and migrate using our own strategy #149282

Closed
exalate-issue-sync bot opened this issue Jan 20, 2023 · 2 comments
Closed
Assignees
Labels
Epic:VersionedAPIs Kibana Versioned APIs Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@exalate-issue-sync
Copy link

Per [~accountid:618111fce79ff6006f0e1417] 's suggestion, we should attempt to apply the strategy we are going to recommend to other teams to our own code base first.

Good candidates are:

  1. Saved Objects Management

  2. Telemtery

@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 20, 2023
@jloleysens jloleysens added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Epic:VersionedAPIs Kibana Versioned APIs labels Jan 20, 2023
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 20, 2023
@jloleysens jloleysens self-assigned this Jan 20, 2023
@rudolf
Copy link
Contributor

rudolf commented Jan 27, 2023

@rudolf rudolf closed this as completed Jan 27, 2023
@rudolf rudolf reopened this Jan 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic:VersionedAPIs Kibana Versioned APIs 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