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

Destroying a user might leave behinds the WorkGroups they created #1431

Open
prioux opened this issue Sep 16, 2024 · 2 comments
Open

Destroying a user might leave behinds the WorkGroups they created #1431

prioux opened this issue Sep 16, 2024 · 2 comments
Labels
Admin Features or bugs related to administrative features Bug

Comments

@prioux
Copy link
Member

prioux commented Sep 16, 2024

The callbacks associated with destroying a user record will prevent the destruction if the user still has any files or tasks.

When the files and tasks have been removed, the user record can be destroyed. However, if the user has created WorkGroups, these are left behind.

The destroy operation should clean up these workgroups.

@prioux prioux added Bug Admin Features or bugs related to administrative features labels Sep 16, 2024
@MontrealSergiy
Copy link
Contributor

@prioux And what should happen to files, dataproviders, etc assigned to that group?

Reset to admin or create a special 'nobody' user?

@prioux
Copy link
Member Author

prioux commented Sep 16, 2024

If the user is about to be deleted, there should be no files belonging to the user, or data providers in the project, because all files and data providers are deleted first.

If there are files belonging to other users (in case of a shared project) then we need a new rule.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Admin Features or bugs related to administrative features Bug
Projects
None yet
Development

No branches or pull requests

2 participants