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

[Fleet] Convert saved objects to be sharable across spaces #99116

Open
jen-huang opened this issue May 3, 2021 · 3 comments
Open

[Fleet] Convert saved objects to be sharable across spaces #99116

jen-huang opened this issue May 3, 2021 · 3 comments
Labels
enhancement New value added to drive a business result Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@jen-huang
Copy link
Contributor

jen-huang commented May 3, 2021

Kibana now has support for sharable saved objects: #27004

Existing saved object types can't take advantage of this new functionality until 8.0 due to breaking changes. Since Kibana assets installed by Fleet are things like dashboards and visualizations, which are generic Kibana SOs, I believe the Kibana team will handle the migration for those. This issue is a placeholder for the Fleet team to double-check that work and revisit Fleet-specific SOs and convert them if necessary.

See #74353 (comment) for some ideas of how this could work from a UX perspective.

@jen-huang jen-huang added enhancement New value added to drive a business result v8.0.0 Team:Fleet Team label for Observability Data Collection Fleet team Breaking Change labels May 3, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@ruflin
Copy link
Member

ruflin commented May 4, 2021

I assume the concept of space agnostic SO will stay around? Would there be any reason to move these to shareable?

@jen-huang
Copy link
Contributor Author

@ruflin Yes, space-agnostic concept will still exist, but it's recommended to use a sharable type in most cases. I'm not sure if it makes sense to use sharable type for Fleet SOs, but it's something to consider now that we have this capability. I recall in the beginning we made everything agnostic for simplicity. For example, maybe certain spaces should only be able to manage certain agent policies and outputs.

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:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

3 participants