-
Notifications
You must be signed in to change notification settings - Fork 182
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
Delete shares from user when user is deleted #1226
Comments
Also, have the same problem with EOS. The shares are not deleted when the user is deleted. Even if we clear the |
It will really help the automated test process if user-cleanup works well. In afterScenario of test scenarios we delete the users in order to give the next scenario a clean start. Otherwise we could adjust the afterScenario of tests so that it first loops through and deletes each share that was created by the user in the scenario, then finally deletes the user. But that won't need to be done if this share cleanup issue is made to work. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
IMO we do not have any special code any more in the test suite for cleaning up shares when a user is deleted. It seems to work OK, at least with the "owncloud" and "ocis" storages that are in automated CI. Maybe this has been all fixed? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
Closing as this is also covered by #1258 - I will check there. |
See https://github.com/owncloud/ocis-reva/issues/262.
We need to remove the user's shares from shares.json and publicshares.json (which act like caches)
Might need some kind of notification system in reva where the deletion/disappearance of a user would propagate an event to all the storage providers so they can proceed to delete any user related metadata.
@butonic
The text was updated successfully, but these errors were encountered: