-
Notifications
You must be signed in to change notification settings - Fork 114
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
update_group behaviour not as expected #217
Comments
To me more precise: |
@bernt-matthias Thanks for the report! It seems this is due to |
Well that is unfortunate. I can't speak for distant-past-@jmchilton - that guy made a ton of mistakes and was kind of a moron - but current @jmchilton doesn't think this should work the way it does. Distant-past-@jmchilton implemented this endpoint with only creating groups and roles in mind. I'm okay with either calling this a bug and just modifying the behavior and hope the backward compatibility doesn't bite anyone or adding a parameter like |
Maybe the main question is if duplicate entries in user_group_accessions in the galaxy DB are a problem. I would vote for the update behavior (as default) since this is documented -- and thereby it should not cause compatibility problems. For the original intended purpose (filling empty groups) update / append make no difference anyway. The additional possibility of append would be a nice addition. |
There is already another API call to add a user to a group in https://github.com/galaxyproject/galaxy/blob/dev/lib/galaxy/webapps/galaxy/api/group_users.py :
Similarly for adding a role to a group. |
Sounds good to me. Unfortunately I can not help with this since I'm not familiar enough with this or the galaxy project. |
The documented behavior of update_group is to substitute previous users. But actually it leads to duplicates of user group associations in the galaxy DB.
This has been tested with version 0.7.0 which is shipped with the current release of galaxy.
The text was updated successfully, but these errors were encountered: