-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Determine what values can come back as BQ access roles #1050
Comments
From the original PR: @fhoffa Is it possible for there to be more than one key in an "access" (ACL) object returned? The spec indicates {
"role": "...",
"userByEmail": "...",
"groupByEmail": "...",
"domain": "...",
"specialGroup": "...",
"view": {
"projectId": "...",
"datasetId": "...",
"tableId": "..."
}
} but empirically @tseaver seems to only be seeing one key and it is always one of |
@jgeewax Is there someone who works on BigQuery we can reach out to? |
bumping internally! |
Thanks @fhoffa! |
BQ engineer here. Every entry in the access list will have exactly one of userByEmail, groupByEmail, domain, specialGroup, or view set. And if anything but view is set, it'll also have a role specified (role is omitted for a view, since views are always read-only, though arguably we should be setting it anyway). This is documented somewhat obliquely by the "[Pick one]" prefix in the field descriptions here: |
Thanks @jcondit! |
@jcondit Thanks I finally got the fix out. It seems https://cloud.google.com/bigquery/access-control#datasetroles could be updated to be more in line with https://cloud.google.com/bigquery/docs/reference/v2/datasets Cheers! |
See #1046
The text was updated successfully, but these errors were encountered: