[DRAFT] Accommodating saved-objects "advanced usage"

[kobelb]

Summary

Saved-objects in Kibana have evolved over the years to take on more and more responsibilities. Saved-objects started as a method of allowing Dashboard, Visualizations and Saved Searches to be persisted in Elasticsearch and have evolved to support much more advanced use-cases like Alerting, Fleet and ML. The advanced use-cases are currently hard to model using saved-objects, and generally lead to purpose-built APIs and Clients which make these entities "saved-objects" but also "not saved-objects".'

The following is a list of functionality that saved-objects in their entirety provide:

• Client-side and Server-side clients
• HTTP APIs
• Saved-object management UI
  • Import
  • Export
  • Copy to Space
  • Share to Space
• Middleware which enables the following:
  • Encrypted saved-objects
  • Spaces to derive the "namespace" from the base-path of the request
  • Security to enforce its authorization rules
• Migrations

[kobelb]

Closing this, a more productive conversation is happening in #72028