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

sql: check privileges in CONFIGURE ZONE commands #5511

Closed
jseldess opened this issue Oct 1, 2019 · 1 comment · Fixed by #5609
Closed

sql: check privileges in CONFIGURE ZONE commands #5511

jseldess opened this issue Oct 1, 2019 · 1 comment · Fixed by #5609
Assignees
Labels
C-product-change P-1 High priority; must be done this release
Milestone

Comments

@jseldess
Copy link
Contributor

jseldess commented Oct 1, 2019

PR: cockroachdb/cockroach#40879

From release notes:

CONFIGURE ZONE statements now fail if the user does not have sufficient privileges. If the target is a system range, the system database, or a table in the system database, the user must have an admin role. For all other databases and tables, the user must have the CREATE privilege on the target database or table. This change might be backward-incompatible for users running scripted CONFIGURE ZONE statements with restricted permissions. To add the necessary permissions, use GRANT <privileges> or GRANT <roles> as a user with an admin role. For example, to grant a user the admin role, run GRANT admin TO <user>. To grant the CREATE privilege on a database or table, run GRANT CREATE ON [DATABASE | TABLE] <name> TO <user>. [#40879][#40879] {% comment %}doc{% endcomment %}

@jseldess jseldess added this to the 19.2 milestone Oct 1, 2019
@jseldess jseldess added A-sql P-1 High priority; must be done this release labels Oct 1, 2019
@ericharmeling
Copy link
Contributor

This was fixed by #5609.

When I merged that PR, I referenced the wrong issue that it fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-product-change P-1 High priority; must be done this release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants