René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Implement: Authorized UDF support for dataset Access","articleBody":"## Overview\r\n\r\nAdd support for authorized UDFs.\r\n\r\nThe Access property of a dataset now allows references to **Routine** entities, similar to the existing View support.  Only UDF routines are currently supported.  This feature is enabled and can be implemented immediately.\r\n\r\n## References\r\n\r\nExample impl: https://github.com/googleapis/google-cloud-go/pull/3084\r\n\r\nWhat we document in the discovery layer for dataset's `access` field:\r\n```\r\n\"access\": {\r\n          \"type\": \"array\",\r\n          \"description\": \"[Optional] An array of objects that define dataset access for one or more entities. You can set this property when inserting or updating a dataset in order to control who is allowed to access the data. If unspecified at dataset creation time, BigQuery adds default dataset access for the following entities: access.specialGroup: projectReaders; access.role: READER; access.specialGroup: projectWriters; access.role: WRITER; access.specialGroup: projectOwners; access.role: OWNER; access.userByEmail: [dataset creator email]; access.role: OWNER;\",\r\n          \"items\": {\r\n            \"properties\": {\r\n              \"view\": {\r\n                \"$ref\": \"TableReference\",\r\n                \"description\": \"[Pick one] A view from a different dataset to grant access to. Queries executed against that view will have read access to tables in this dataset. The role field is not required when this field is set. If that view is updated by any user, access to the view needs to be granted again via an update operation.\"\r\n              },\r\n              \"groupByEmail\": {\r\n                \"description\": \"[Pick one] An email address of a Google Group to grant access to. Maps to IAM policy member \\\"group:GROUP\\\".\",\r\n                \"type\": \"string\"\r\n              },\r\n              \"userByEmail\": {\r\n                \"description\": \"[Pick one] An email address of a user to grant access to. For example: fred@example.com. Maps to IAM policy member \\\"user:EMAIL\\\" or \\\"serviceAccount:EMAIL\\\".\",\r\n                \"type\": \"string\"\r\n              },\r\n              \"domain\": {\r\n                \"description\": \"[Pick one] A domain to grant access to. Any users signed in with the domain specified will be granted the specified access. Example: \\\"example.com\\\". Maps to IAM policy member \\\"domain:DOMAIN\\\".\",\r\n                \"type\": \"string\"\r\n              },\r\n              \"iamMember\": {\r\n                \"type\": \"string\",\r\n                \"description\": \"[Pick one] Some other type of member that appears in the IAM Policy but isn't a user, group, domain, or special group.\"\r\n              },\r\n              \"role\": {\r\n                \"description\": \"[Required] An IAM role ID that should be granted to the user, group, or domain specified in this access entry. The following legacy mappings will be applied: OWNER  roles/bigquery.dataOwner WRITER  roles/bigquery.dataEditor READER  roles/bigquery.dataViewer This field will accept any of the above formats, but will return only the legacy format. For example, if you set this field to \\\"roles/bigquery.dataOwner\\\", it will be returned back as \\\"OWNER\\\".\",\r\n                \"type\": \"string\"\r\n              },\r\n              \"specialGroup\": {\r\n                \"type\": \"string\",\r\n                \"description\": \"[Pick one] A special group to grant access to. Possible values include: projectOwners: Owners of the enclosing project. projectReaders: Readers of the enclosing project. projectWriters: Writers of the enclosing project. allAuthenticatedUsers: All authenticated BigQuery users. Maps to similarly-named IAM members.\"\r\n              },\r\n              \"routine\": {\r\n                \"$ref\": \"RoutineReference\",\r\n                \"description\": \"[Pick one] A routine from a different dataset to grant access to. Queries executed against that routine will have read access to views/tables/routines in this dataset. Only UDF is supported for now. The role field is not required when this field is set. If that routine is updated by any user, access to the routine needs to be granted again via an update operation.\"\r\n              }\r\n            },\r\n            \"type\": \"object\"\r\n          }\r\n        },\r\n```\r\n\r\nInternal request issue: 170647386\r\n","author":{"url":"https://github.com/shollyman","@type":"Person","name":"shollyman"},"datePublished":"2020-10-29T20:19:56.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/353/python-bigquery/issues/353"}