-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
sql: remove connect privilege warning #61568
sql: remove connect privilege warning #61568
Conversation
Release justification: No functionality, removing warning Release note: None
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.
lgtm! thoughts on giving the admin
role the connect privilege?
However it does not for the system db though as admin is only given GRANT/SELECT on it. We should give it CONNECT though, I'll open a separate PR for it. I think we also need a migration to give CONNECT to admin for system dbs created before 21.1. Thoughts? |
Thanks for the review! |
Wait oops, I'll wait for CI to pass first |
Canceled. |
bors r=rafiss |
Build failed: |
bors r=rafiss |
Hmm yes I suppose we should. I guess if it's annoying to do we can always push it off until we decide to enforce CONNECT privilege rules. lol or maybe we should just hardcode every role/user to have CONNECT privilege and make it impossible to revoke.... |
Build succeeded: |
I don't think it would be annoying to do the migration, I wouldn't say it's urgent or necessary as of now as CONNECT only allows users to see metadata and admin can already see metadata on the system database anyway. |
sql: remove connect privilege warning
Release justification: No functionality, removing warning
Release note: None
Resolves #61560