-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[SECURITY] Copy saved object flyout should not allow copying into the active space #116657
[SECURITY] Copy saved object flyout should not allow copying into the active space #116657
Conversation
Pinging @elastic/kibana-security (Team:Security) |
My diligent on the stress: https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/2111/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Thanks!
…_space_flyout_internal
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @XavierM |
… active space (elastic#116657) * copy saved object flyout should not allow copying into the active space * stupid me
… active space (elastic#116657) * copy saved object flyout should not allow copying into the active space * stupid me
… active space (#116657) (#116818) * copy saved object flyout should not allow copying into the active space * stupid me Co-authored-by: Xavier Mouligneau <[email protected]>
… active space (#116657) (#116817) * copy saved object flyout should not allow copying into the active space * stupid me Co-authored-by: Xavier Mouligneau <[email protected]>
Summary
The fly-out should exclude the active space from the list of target spaces. If there are no target spaces, the fly-out should inform you that there are no other spaces to copy this object.
I stress out these tests but I was not able to reproduce it, I think the refactor from @jportner made these tests more stable 😍
Resolves: #116650 #96708
Checklist