-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add Group Metadata #122
Add Group Metadata #122
Conversation
BASE_POLICY_UNSPECIFIED = 0; | ||
BASE_POLICY_ALLOW = 1; | ||
BASE_POLICY_DENY = 2; | ||
BASE_POLICY_ALLOW_SAME_MEMBER = 3; |
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.
This would only be used for removing members right? Is there any case where it would be permissible for this to NOT be set for removing members?
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.
Probably not. Think that one would be pretty uniform.
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 think having this specified as a policy, rather than baked directly into the code, means a malicious person could potentially create a group with this option turned off (no self removal allowed)? I guess my instinct with these changes is to expose the minimum amount for developers to have the features they desire, rather than having maximum flexibility
@richardhuaaa I've removed the |
@richardhuaaa I've removed the Add/Remove installation policies, so the policies are just for members right now. |
🎉 This PR is included in version 3.36.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Summary