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

fix #3654: jupyterhub moderation requests #4211

Merged
merged 1 commit into from
May 30, 2022

Conversation

rorour
Copy link
Contributor

@rorour rorour commented Mar 4, 2022

No description provided.

@rorour rorour requested a review from e-carlin March 4, 2022 18:39
@robnagler robnagler self-assigned this Mar 7, 2022
Copy link
Member

@robnagler robnagler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First set of comments. I would like to discuss parse_post.require_sim_type.

@rorour rorour force-pushed the 3654-moderate-jupyterhub-user-creations branch 2 times, most recently from b65eed7 to 84a51a4 Compare March 9, 2022 23:33
@e-carlin
Copy link
Member

Reminding myself - we need to write a migration for existing users

Copy link
Member

@robnagler robnagler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

More comments. I didn't finish. LMK when you are ready for another review.

@rorour rorour requested a review from robnagler March 18, 2022 21:54
Copy link
Member

@robnagler robnagler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be good to walk through these changes together. I have particular opinions here that may need more explanations.

@rorour rorour requested a review from robnagler March 24, 2022 17:57
Copy link
Member

@robnagler robnagler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I backtracked on some decisions and added more feedback. I'm being pedantic, because there are a lot of interesting coding and testing cases.

@rorour rorour requested a review from robnagler March 28, 2022 21:51
Copy link
Member

@robnagler robnagler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I should help with this. Set up a meeting when you want to work on this.

@rorour
Copy link
Contributor Author

rorour commented Mar 29, 2022

@robnagler where should we check for guest users to keep them from accessing the moderation apis?

@rorour rorour force-pushed the 3654-moderate-jupyterhub-user-creations branch from 06a9302 to 3e86c22 Compare April 11, 2022 16:05
@rorour rorour requested a review from robnagler April 11, 2022 16:06
@e-carlin
Copy link
Member

@robnagler ready for another review

@e-carlin e-carlin requested a review from robnagler April 25, 2022 19:49
Copy link
Member

@robnagler robnagler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is good to go. Is there a migration for users? Do you want to push to alpha?

@e-carlin
Copy link
Member

Yes a migration needs to be written, thanks for the reminder. I'll add that then we can merge.

@e-carlin
Copy link
Member

Thinking about this more, no migration is needed. User's who are in the approved community pool already have the sim_type_jupyterhublogin role. So, things will continue to work like normal for them. User's who are in the denied list (not actually used anywhere currently but we kept it around) don't have any records in the db so we have no way of finding a uid for them and setting them as denied in user_role_invite_t. So, I think we're good to go. Please confirm and I'll merge.

@e-carlin e-carlin force-pushed the 3654-moderate-jupyterhub-user-creations branch 2 times, most recently from b0a1f12 to 2bb8368 Compare April 28, 2022 20:25
@robnagler
Copy link
Member

Did you run a check for the denied list? I think we should run this check: validate that only users in valid pools (uspas, etc.) have the role. Any users not in these pools should get role removed.

We need to migrate from the community pool to the everybody pool once moderation is released to production. We still need pools for uspas, etc.

@e-carlin e-carlin force-pushed the 3654-moderate-jupyterhub-user-creations branch 2 times, most recently from e785b29 to 19e2293 Compare May 24, 2022 20:43
@e-carlin
Copy link
Member

@robnagler I've written a script (hand/check-jupyter-users/check-jupyter-users.sh) to do the validation. You can run it as is (only does reads currently). I left a TODO with a question at the top. If you could answer as well as do a full review of the script (I'd really like to improve my bash) I'd appreciate it.

@e-carlin e-carlin force-pushed the 3654-moderate-jupyterhub-user-creations branch 2 times, most recently from ad20d6b to 2b6c814 Compare May 27, 2022 19:34
@e-carlin e-carlin force-pushed the 3654-moderate-jupyterhub-user-creations branch from 2b6c814 to ed15491 Compare May 30, 2022 20:54
@e-carlin e-carlin merged commit 5d2d18a into master May 30, 2022
@e-carlin e-carlin deleted the 3654-moderate-jupyterhub-user-creations branch May 30, 2022 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants