resource"google_bigquery_dataset""default"{dataset_id="foo"friendly_name="test"description="This is a test description"location="EU"default_table_expiration_ms=3600000labels{env="default"}access{role="READER"domain="example.com"}access{role="WRITER"group_by_email="writers@example.com"}}

There are two types of locations, regional or multi-regional.
A regional location is a specific geographic place, such as Tokyo, and a
multi-regional location is a large geographic area, such as the United States,
that contains at least two geographic places

The default value is multi-regional location US.
Changing this forces a new resource to be created.

default_table_expiration_ms - (Optional) The default lifetime of all
tables in the dataset, in milliseconds. The minimum value is 3600000
milliseconds (one hour).

Once this property is set, all newly-created
tables in the dataset will have an expirationTime property set to the
creation time plus the value in this property, and changing the value
will only affect new tables, not existing ones. When the
expirationTime for a given table is reached, that table will be
deleted automatically. If a table's expirationTime is modified or
removed before the table expires, or if you provide an explicit
expirationTime when creating a table, that value takes precedence
over the default expiration time indicated by this property.

access - (Optional) An array of objects that define dataset access for
one or more entities. Structure is documented below.

The access block supports the following fields (exactly one of domain,
group_by_email, special_group, user_by_email, or view must be set,
even though they are marked optional):
* role - (Required unless view is set) Describes the rights granted to
the user specified by the other member of the access object. The following
string values are supported: READER, WRITER, OWNER.

user_by_email - (Optional) An email address of a user to grant access to.

view - (Optional) 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. Structure is documented below.

The access.view block supports:
* dataset_id - (Required) The ID of the dataset containing this table.