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

Provide results when Saved Objects are shared or unshared #74989

Closed
jportner opened this issue Aug 13, 2020 · 1 comment · Fixed by #74995
Closed

Provide results when Saved Objects are shared or unshared #74989

jportner opened this issue Aug 13, 2020 · 1 comment · Fixed by #74995
Assignees
Labels
enhancement New value added to drive a business result Feature:Saved Objects Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@jportner
Copy link
Contributor

jportner commented Aug 13, 2020

Currently, when sharing or unsharing saved objects (via the Saved Objects Client's addToNamespaces and deleteFromNamespaces methods), the result is an empty object. This is because all planned consumers did not need any additional information; there is precedent for this, as the delete method works the same way.

However, when starting work on #54836, it became clear that we need to be able to identify what namespaces an object exists in after the operation completes to generate the audit events with the proper level of detail.

@jportner jportner added Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! enhancement New value added to drive a business result labels Aug 13, 2020
@jportner jportner self-assigned this Aug 13, 2020
@elasticmachine
Copy link
Contributor

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

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 Feature:Saved Objects Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants