-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Only allow removing existing shares that would not be allowed due to reshare restrictions #26571
Conversation
I've pushed two more commits to get the discussion for my proposal some example here to
|
@rullzer Maybe you can share your opinion on this :) |
44d5e22
to
2824cce
Compare
2824cce
to
4810ec9
Compare
b872c2f
to
140dd42
Compare
Is it still "to review" ? |
Would be ready for review, though after my rebase today i guess i need to have another look at the one failing acceptance test which seems related, which would cover exactly that case where now a share would be cleaned up:
|
140dd42
to
64d6655
Compare
Signed-off-by: Julius Härtl <jus@bitgrid.net>
Signed-off-by: Julius Härtl <jus@bitgrid.net>
…reshare restrictions Signed-off-by: Julius Härtl <jus@bitgrid.net>
Signed-off-by: Julius Härtl <jus@bitgrid.net>
64d6655
to
964fd27
Compare
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.
I probably don't have the full picture, but the code looks fine :).
do we need backports? |
/backport to stable21 |
/backport to stable20 |
/backport to stable19 |
The backport to stable19 failed. Please do this backport manually. |
Steps to reproduce:
The share link still exists in the user interface though it is no longer accessible due to the missing reshare permissions on the parent share.
This PR makes sure that the UI doesn't offer to modify the link share and only remove it which is still possible.
However I'm still wondering if we should either indicate that this share is stale in the UI or even remove the share link if the node is moved to a share without reshare permissions, but not sure if dropping those shares automatically would be something feasible.