Entry

Entry Metadata. A Data Catalog Entry resource represents another resource in Google Cloud Platform (such as a BigQuery dataset or a Pub/Sub topic) or outside of Google Cloud Platform. Clients can use the linkedResource field in the Entry resource to refer to the original resource ID of the source system.

An Entry resource contains resource details, such as its schema. An Entry can also be used to attach flexible metadata, such as a Tag.

To get more information about Entry, see:

API documentation
How-to Guides
- Official Documentation

Create a Entry Resource

new Entry(name: string, args: EntryArgs, opts?: CustomResourceOptions);

def Entry(resource_name, opts=None, description=None, display_name=None, entry_group=None, entry_id=None, gcs_fileset_spec=None, linked_resource=None, schema=None, type=None, user_specified_system=None, user_specified_type=None, __props__=None);

func NewEntry(ctx *Context, name string, args EntryArgs, opts ...ResourceOption) (*Entry, error)

public Entry(string name, EntryArgs args, CustomResourceOptions? opts = null)

name string: The unique name of the resource.
args EntryArgs: The arguments to resource properties.
opts CustomResourceOptions: Bag of options to control resource's behavior.

resource_name str: The unique name of the resource.
opts ResourceOptions: A bag of options that control this resource's behavior.

ctx Context: Context object for the current deployment.
name string: The unique name of the resource.
args EntryArgs: The arguments to resource properties.
opts ResourceOption: Bag of options to control resource's behavior.

name string: The unique name of the resource.
args EntryArgs: The arguments to resource properties.
opts CustomResourceOptions: Bag of options to control resource's behavior.

Entry Resource Properties

To learn more about resource properties and how to use them, see Inputs and Outputs in the Programming Model docs.

Inputs

The Entry resource accepts the following input properties:

EntryGroup string: The name of the entry group this entry is in.
EntryId string: The id of the entry to create.
Description string: Entry description, which can consist of several sentences or paragraphs that describe entry contents.
DisplayName string: Display information such as title and description. A short name to identify the entry, for example, “Analytics Data - Jan 2011”.
GcsFilesetSpec EntryGcsFilesetSpecArgs: Specification that applies to a Cloud Storage fileset. This is only valid on entries of type FILESET. Structure is documented below.
LinkedResource string: The resource this metadata entry refers to. For Google Cloud Platform resources, linkedResource is the full name of the resource. For example, the linkedResource for a table resource from BigQuery is: //bigquery.googleapis.com/projects/projectId/datasets/datasetId/tables/tableId Output only when Entry is of type in the EntryType enum. For entries with userSpecifiedType, this field is optional and defaults to an empty string.
Schema string: Schema of the entry (e.g. BigQuery, GoogleSQL, Avro schema), as a json string. An entry might not have any schema attached to it. See https://cloud.google.com/data-catalog/docs/reference/rest/v1/projects.locations.entryGroups.entries#schema for what fields this schema can contain.
Type string: The type of the entry. Only used for Entries with types in the EntryType enum. Currently, only FILESET enum value is allowed. All other entries created through Data Catalog must use userSpecifiedType.
UserSpecifiedSystem string: This field indicates the entry’s source system that Data Catalog does not integrate with. userSpecifiedSystem strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.
UserSpecifiedType string: Entry type if it does not fit any of the input-allowed values listed in EntryType enum above. When creating an entry, users should check the enum values first, if nothing matches the entry to be created, then provide a custom value, for example “my_special_type”. userSpecifiedType strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.

EntryGroup string: The name of the entry group this entry is in.
EntryId string: The id of the entry to create.
Description string: Entry description, which can consist of several sentences or paragraphs that describe entry contents.
DisplayName string: Display information such as title and description. A short name to identify the entry, for example, “Analytics Data - Jan 2011”.
GcsFilesetSpec EntryGcsFilesetSpec: Specification that applies to a Cloud Storage fileset. This is only valid on entries of type FILESET. Structure is documented below.
LinkedResource string: The resource this metadata entry refers to. For Google Cloud Platform resources, linkedResource is the full name of the resource. For example, the linkedResource for a table resource from BigQuery is: //bigquery.googleapis.com/projects/projectId/datasets/datasetId/tables/tableId Output only when Entry is of type in the EntryType enum. For entries with userSpecifiedType, this field is optional and defaults to an empty string.
Schema string: Schema of the entry (e.g. BigQuery, GoogleSQL, Avro schema), as a json string. An entry might not have any schema attached to it. See https://cloud.google.com/data-catalog/docs/reference/rest/v1/projects.locations.entryGroups.entries#schema for what fields this schema can contain.
Type string: The type of the entry. Only used for Entries with types in the EntryType enum. Currently, only FILESET enum value is allowed. All other entries created through Data Catalog must use userSpecifiedType.
UserSpecifiedSystem string: This field indicates the entry’s source system that Data Catalog does not integrate with. userSpecifiedSystem strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.
UserSpecifiedType string: Entry type if it does not fit any of the input-allowed values listed in EntryType enum above. When creating an entry, users should check the enum values first, if nothing matches the entry to be created, then provide a custom value, for example “my_special_type”. userSpecifiedType strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.

entryGroup string: The name of the entry group this entry is in.
entryId string: The id of the entry to create.
description string: Entry description, which can consist of several sentences or paragraphs that describe entry contents.
displayName string: Display information such as title and description. A short name to identify the entry, for example, “Analytics Data - Jan 2011”.
gcsFilesetSpec EntryGcsFilesetSpec: Specification that applies to a Cloud Storage fileset. This is only valid on entries of type FILESET. Structure is documented below.
linkedResource string: The resource this metadata entry refers to. For Google Cloud Platform resources, linkedResource is the full name of the resource. For example, the linkedResource for a table resource from BigQuery is: //bigquery.googleapis.com/projects/projectId/datasets/datasetId/tables/tableId Output only when Entry is of type in the EntryType enum. For entries with userSpecifiedType, this field is optional and defaults to an empty string.
schema string: Schema of the entry (e.g. BigQuery, GoogleSQL, Avro schema), as a json string. An entry might not have any schema attached to it. See https://cloud.google.com/data-catalog/docs/reference/rest/v1/projects.locations.entryGroups.entries#schema for what fields this schema can contain.
type string: The type of the entry. Only used for Entries with types in the EntryType enum. Currently, only FILESET enum value is allowed. All other entries created through Data Catalog must use userSpecifiedType.
userSpecifiedSystem string: This field indicates the entry’s source system that Data Catalog does not integrate with. userSpecifiedSystem strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.
userSpecifiedType string: Entry type if it does not fit any of the input-allowed values listed in EntryType enum above. When creating an entry, users should check the enum values first, if nothing matches the entry to be created, then provide a custom value, for example “my_special_type”. userSpecifiedType strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.

entry_group str: The name of the entry group this entry is in.
entry_id str: The id of the entry to create.
description str: Entry description, which can consist of several sentences or paragraphs that describe entry contents.
display_name str: Display information such as title and description. A short name to identify the entry, for example, “Analytics Data - Jan 2011”.
gcs_fileset_spec Dict[EntryGcsFilesetSpec]: Specification that applies to a Cloud Storage fileset. This is only valid on entries of type FILESET. Structure is documented below.
linked_resource str: The resource this metadata entry refers to. For Google Cloud Platform resources, linkedResource is the full name of the resource. For example, the linkedResource for a table resource from BigQuery is: //bigquery.googleapis.com/projects/projectId/datasets/datasetId/tables/tableId Output only when Entry is of type in the EntryType enum. For entries with userSpecifiedType, this field is optional and defaults to an empty string.
schema str: Schema of the entry (e.g. BigQuery, GoogleSQL, Avro schema), as a json string. An entry might not have any schema attached to it. See https://cloud.google.com/data-catalog/docs/reference/rest/v1/projects.locations.entryGroups.entries#schema for what fields this schema can contain.
type str: The type of the entry. Only used for Entries with types in the EntryType enum. Currently, only FILESET enum value is allowed. All other entries created through Data Catalog must use userSpecifiedType.
user_specified_system str: This field indicates the entry’s source system that Data Catalog does not integrate with. userSpecifiedSystem strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.
user_specified_type str: Entry type if it does not fit any of the input-allowed values listed in EntryType enum above. When creating an entry, users should check the enum values first, if nothing matches the entry to be created, then provide a custom value, for example “my_special_type”. userSpecifiedType strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.

Outputs

All input properties are implicitly available as output properties. Additionally, the Entry resource produces the following output properties:

BigqueryDateShardedSpec EntryBigqueryDateShardedSpec: Specification for a group of BigQuery tables with name pattern [prefix]YYYYMMDD. Context: https://cloud.google.com/bigquery/docs/partitioned-tables#partitioning_versus_sharding.
BigqueryTableSpec EntryBigqueryTableSpec: Specification that applies to a BigQuery table. This is only valid on entries of type TABLE.
Id string: The provider-assigned unique ID for this managed resource.
IntegratedSystem string: This field indicates the entry’s source system that Data Catalog integrates with, such as BigQuery or Pub/Sub.
Name string: The Data Catalog resource name of the entry in URL format. Example: projects/{project_id}/locations/{location}/entryGroups/{entryGroupId}/entries/{entryId}. Note that this Entry and its child resources may not actually be stored in the location in this name.

BigqueryDateShardedSpec EntryBigqueryDateShardedSpec: Specification for a group of BigQuery tables with name pattern [prefix]YYYYMMDD. Context: https://cloud.google.com/bigquery/docs/partitioned-tables#partitioning_versus_sharding.
BigqueryTableSpec EntryBigqueryTableSpec: Specification that applies to a BigQuery table. This is only valid on entries of type TABLE.
Id string: The provider-assigned unique ID for this managed resource.
IntegratedSystem string: This field indicates the entry’s source system that Data Catalog integrates with, such as BigQuery or Pub/Sub.
Name string: The Data Catalog resource name of the entry in URL format. Example: projects/{project_id}/locations/{location}/entryGroups/{entryGroupId}/entries/{entryId}. Note that this Entry and its child resources may not actually be stored in the location in this name.

bigqueryDateShardedSpec EntryBigqueryDateShardedSpec: Specification for a group of BigQuery tables with name pattern [prefix]YYYYMMDD. Context: https://cloud.google.com/bigquery/docs/partitioned-tables#partitioning_versus_sharding.
bigqueryTableSpec EntryBigqueryTableSpec: Specification that applies to a BigQuery table. This is only valid on entries of type TABLE.
id string: The provider-assigned unique ID for this managed resource.
integratedSystem string: This field indicates the entry’s source system that Data Catalog integrates with, such as BigQuery or Pub/Sub.
name string: The Data Catalog resource name of the entry in URL format. Example: projects/{project_id}/locations/{location}/entryGroups/{entryGroupId}/entries/{entryId}. Note that this Entry and its child resources may not actually be stored in the location in this name.

bigquery_date_sharded_spec Dict[EntryBigqueryDateShardedSpec]: Specification for a group of BigQuery tables with name pattern [prefix]YYYYMMDD. Context: https://cloud.google.com/bigquery/docs/partitioned-tables#partitioning_versus_sharding.
bigquery_table_spec Dict[EntryBigqueryTableSpec]: Specification that applies to a BigQuery table. This is only valid on entries of type TABLE.
id str: The provider-assigned unique ID for this managed resource.
integrated_system str: This field indicates the entry’s source system that Data Catalog integrates with, such as BigQuery or Pub/Sub.
name str: The Data Catalog resource name of the entry in URL format. Example: projects/{project_id}/locations/{location}/entryGroups/{entryGroupId}/entries/{entryId}. Note that this Entry and its child resources may not actually be stored in the location in this name.

Look up an Existing Entry Resource

Get an existing Entry resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.

public static get(name: string, id: Input<ID>, state?: EntryState, opts?: CustomResourceOptions): Entry

static get(resource_name, id, opts=None, bigquery_date_sharded_spec=None, bigquery_table_spec=None, description=None, display_name=None, entry_group=None, entry_id=None, gcs_fileset_spec=None, integrated_system=None, linked_resource=None, name=None, schema=None, type=None, user_specified_system=None, user_specified_type=None, __props__=None);

func GetEntry(ctx *Context, name string, id IDInput, state *EntryState, opts ...ResourceOption) (*Entry, error)

public static Entry Get(string name, Input<string> id, EntryState? state, CustomResourceOptions? opts = null)

name: The unique name of the resulting resource.
id: The unique provider ID of the resource to lookup.
state: Any extra arguments used during the lookup.
opts: A bag of options that control this resource's behavior.

resource_name: The unique name of the resulting resource.
id: The unique provider ID of the resource to lookup.

name: The unique name of the resulting resource.
id: The unique provider ID of the resource to lookup.
state: Any extra arguments used during the lookup.
opts: A bag of options that control this resource's behavior.

name: The unique name of the resulting resource.
id: The unique provider ID of the resource to lookup.
state: Any extra arguments used during the lookup.
opts: A bag of options that control this resource's behavior.

The following state arguments are supported:

BigqueryDateShardedSpec EntryBigqueryDateShardedSpecArgs: Specification for a group of BigQuery tables with name pattern [prefix]YYYYMMDD. Context: https://cloud.google.com/bigquery/docs/partitioned-tables#partitioning_versus_sharding.
BigqueryTableSpec EntryBigqueryTableSpecArgs: Specification that applies to a BigQuery table. This is only valid on entries of type TABLE.
Description string: Entry description, which can consist of several sentences or paragraphs that describe entry contents.
DisplayName string: Display information such as title and description. A short name to identify the entry, for example, “Analytics Data - Jan 2011”.
EntryGroup string: The name of the entry group this entry is in.
EntryId string: The id of the entry to create.
GcsFilesetSpec EntryGcsFilesetSpecArgs: Specification that applies to a Cloud Storage fileset. This is only valid on entries of type FILESET. Structure is documented below.
IntegratedSystem string: This field indicates the entry’s source system that Data Catalog integrates with, such as BigQuery or Pub/Sub.
LinkedResource string: The resource this metadata entry refers to. For Google Cloud Platform resources, linkedResource is the full name of the resource. For example, the linkedResource for a table resource from BigQuery is: //bigquery.googleapis.com/projects/projectId/datasets/datasetId/tables/tableId Output only when Entry is of type in the EntryType enum. For entries with userSpecifiedType, this field is optional and defaults to an empty string.
Name string: The Data Catalog resource name of the entry in URL format. Example: projects/{project_id}/locations/{location}/entryGroups/{entryGroupId}/entries/{entryId}. Note that this Entry and its child resources may not actually be stored in the location in this name.
Schema string: Schema of the entry (e.g. BigQuery, GoogleSQL, Avro schema), as a json string. An entry might not have any schema attached to it. See https://cloud.google.com/data-catalog/docs/reference/rest/v1/projects.locations.entryGroups.entries#schema for what fields this schema can contain.
Type string: The type of the entry. Only used for Entries with types in the EntryType enum. Currently, only FILESET enum value is allowed. All other entries created through Data Catalog must use userSpecifiedType.
UserSpecifiedSystem string: This field indicates the entry’s source system that Data Catalog does not integrate with. userSpecifiedSystem strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.
UserSpecifiedType string: Entry type if it does not fit any of the input-allowed values listed in EntryType enum above. When creating an entry, users should check the enum values first, if nothing matches the entry to be created, then provide a custom value, for example “my_special_type”. userSpecifiedType strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.

BigqueryDateShardedSpec EntryBigqueryDateShardedSpec: Specification for a group of BigQuery tables with name pattern [prefix]YYYYMMDD. Context: https://cloud.google.com/bigquery/docs/partitioned-tables#partitioning_versus_sharding.
BigqueryTableSpec EntryBigqueryTableSpec: Specification that applies to a BigQuery table. This is only valid on entries of type TABLE.
Description string: Entry description, which can consist of several sentences or paragraphs that describe entry contents.
DisplayName string: Display information such as title and description. A short name to identify the entry, for example, “Analytics Data - Jan 2011”.
EntryGroup string: The name of the entry group this entry is in.
EntryId string: The id of the entry to create.
GcsFilesetSpec EntryGcsFilesetSpec: Specification that applies to a Cloud Storage fileset. This is only valid on entries of type FILESET. Structure is documented below.
IntegratedSystem string: This field indicates the entry’s source system that Data Catalog integrates with, such as BigQuery or Pub/Sub.
LinkedResource string: The resource this metadata entry refers to. For Google Cloud Platform resources, linkedResource is the full name of the resource. For example, the linkedResource for a table resource from BigQuery is: //bigquery.googleapis.com/projects/projectId/datasets/datasetId/tables/tableId Output only when Entry is of type in the EntryType enum. For entries with userSpecifiedType, this field is optional and defaults to an empty string.
Name string: The Data Catalog resource name of the entry in URL format. Example: projects/{project_id}/locations/{location}/entryGroups/{entryGroupId}/entries/{entryId}. Note that this Entry and its child resources may not actually be stored in the location in this name.
Schema string: Schema of the entry (e.g. BigQuery, GoogleSQL, Avro schema), as a json string. An entry might not have any schema attached to it. See https://cloud.google.com/data-catalog/docs/reference/rest/v1/projects.locations.entryGroups.entries#schema for what fields this schema can contain.
Type string: The type of the entry. Only used for Entries with types in the EntryType enum. Currently, only FILESET enum value is allowed. All other entries created through Data Catalog must use userSpecifiedType.
UserSpecifiedSystem string: This field indicates the entry’s source system that Data Catalog does not integrate with. userSpecifiedSystem strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.
UserSpecifiedType string: Entry type if it does not fit any of the input-allowed values listed in EntryType enum above. When creating an entry, users should check the enum values first, if nothing matches the entry to be created, then provide a custom value, for example “my_special_type”. userSpecifiedType strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.

bigqueryDateShardedSpec EntryBigqueryDateShardedSpec: Specification for a group of BigQuery tables with name pattern [prefix]YYYYMMDD. Context: https://cloud.google.com/bigquery/docs/partitioned-tables#partitioning_versus_sharding.
bigqueryTableSpec EntryBigqueryTableSpec: Specification that applies to a BigQuery table. This is only valid on entries of type TABLE.
description string: Entry description, which can consist of several sentences or paragraphs that describe entry contents.
displayName string: Display information such as title and description. A short name to identify the entry, for example, “Analytics Data - Jan 2011”.
entryGroup string: The name of the entry group this entry is in.
entryId string: The id of the entry to create.
gcsFilesetSpec EntryGcsFilesetSpec: Specification that applies to a Cloud Storage fileset. This is only valid on entries of type FILESET. Structure is documented below.
integratedSystem string: This field indicates the entry’s source system that Data Catalog integrates with, such as BigQuery or Pub/Sub.
linkedResource string: The resource this metadata entry refers to. For Google Cloud Platform resources, linkedResource is the full name of the resource. For example, the linkedResource for a table resource from BigQuery is: //bigquery.googleapis.com/projects/projectId/datasets/datasetId/tables/tableId Output only when Entry is of type in the EntryType enum. For entries with userSpecifiedType, this field is optional and defaults to an empty string.
name string: The Data Catalog resource name of the entry in URL format. Example: projects/{project_id}/locations/{location}/entryGroups/{entryGroupId}/entries/{entryId}. Note that this Entry and its child resources may not actually be stored in the location in this name.
schema string: Schema of the entry (e.g. BigQuery, GoogleSQL, Avro schema), as a json string. An entry might not have any schema attached to it. See https://cloud.google.com/data-catalog/docs/reference/rest/v1/projects.locations.entryGroups.entries#schema for what fields this schema can contain.
type string: The type of the entry. Only used for Entries with types in the EntryType enum. Currently, only FILESET enum value is allowed. All other entries created through Data Catalog must use userSpecifiedType.
userSpecifiedSystem string: This field indicates the entry’s source system that Data Catalog does not integrate with. userSpecifiedSystem strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.
userSpecifiedType string: Entry type if it does not fit any of the input-allowed values listed in EntryType enum above. When creating an entry, users should check the enum values first, if nothing matches the entry to be created, then provide a custom value, for example “my_special_type”. userSpecifiedType strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.

bigquery_date_sharded_spec Dict[EntryBigqueryDateShardedSpec]: Specification for a group of BigQuery tables with name pattern [prefix]YYYYMMDD. Context: https://cloud.google.com/bigquery/docs/partitioned-tables#partitioning_versus_sharding.
bigquery_table_spec Dict[EntryBigqueryTableSpec]: Specification that applies to a BigQuery table. This is only valid on entries of type TABLE.
description str: Entry description, which can consist of several sentences or paragraphs that describe entry contents.
display_name str: Display information such as title and description. A short name to identify the entry, for example, “Analytics Data - Jan 2011”.
entry_group str: The name of the entry group this entry is in.
entry_id str: The id of the entry to create.
gcs_fileset_spec Dict[EntryGcsFilesetSpec]: Specification that applies to a Cloud Storage fileset. This is only valid on entries of type FILESET. Structure is documented below.
integrated_system str: This field indicates the entry’s source system that Data Catalog integrates with, such as BigQuery or Pub/Sub.
linked_resource str: The resource this metadata entry refers to. For Google Cloud Platform resources, linkedResource is the full name of the resource. For example, the linkedResource for a table resource from BigQuery is: //bigquery.googleapis.com/projects/projectId/datasets/datasetId/tables/tableId Output only when Entry is of type in the EntryType enum. For entries with userSpecifiedType, this field is optional and defaults to an empty string.
name str: The Data Catalog resource name of the entry in URL format. Example: projects/{project_id}/locations/{location}/entryGroups/{entryGroupId}/entries/{entryId}. Note that this Entry and its child resources may not actually be stored in the location in this name.
schema str: Schema of the entry (e.g. BigQuery, GoogleSQL, Avro schema), as a json string. An entry might not have any schema attached to it. See https://cloud.google.com/data-catalog/docs/reference/rest/v1/projects.locations.entryGroups.entries#schema for what fields this schema can contain.
type str: The type of the entry. Only used for Entries with types in the EntryType enum. Currently, only FILESET enum value is allowed. All other entries created through Data Catalog must use userSpecifiedType.
user_specified_system str: This field indicates the entry’s source system that Data Catalog does not integrate with. userSpecifiedSystem strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.
user_specified_type str: Entry type if it does not fit any of the input-allowed values listed in EntryType enum above. When creating an entry, users should check the enum values first, if nothing matches the entry to be created, then provide a custom value, for example “my_special_type”. userSpecifiedType strings must begin with a letter or underscore and can only contain letters, numbers, and underscores; are case insensitive; must be at least 1 character and at most 64 characters long.

Supporting Types

EntryBigqueryDateShardedSpec

See the output API doc for this type.

Dataset string
ShardCount int
TablePrefix string

Dataset string
ShardCount int
TablePrefix string

dataset string
shardCount number
tablePrefix string

dataset str
shardCount float
tablePrefix str

EntryBigqueryTableSpec

See the output API doc for this type.

TableSourceType string
TableSpec EntryBigqueryTableSpecTableSpecArgs
ViewSpec EntryBigqueryTableSpecViewSpecArgs

TableSourceType string
TableSpec EntryBigqueryTableSpecTableSpec
ViewSpec EntryBigqueryTableSpecViewSpec

tableSourceType string
tableSpec EntryBigqueryTableSpecTableSpec
viewSpec EntryBigqueryTableSpecViewSpec

tableSourceType str
tableSpec Dict[EntryBigqueryTableSpecTableSpec]
viewSpec Dict[EntryBigqueryTableSpecViewSpec]

EntryBigqueryTableSpecTableSpec

See the output API doc for this type.

GroupedEntry string

GroupedEntry string

groupedEntry string

groupedEntry str

EntryBigqueryTableSpecViewSpec

See the output API doc for this type.

ViewQuery string

ViewQuery string

viewQuery string

viewQuery str

EntryGcsFilesetSpec

See the input and output API doc for this type.

FilePatterns List<string>: Patterns to identify a set of files in Google Cloud Storage. See Cloud Storage documentation for more information. Note that bucket wildcards are currently not supported. Examples of valid filePatterns: * gs://bucket_name/dir/*: matches all files within bucket_name/dir directory. * gs://bucket_name/dir/**: matches all files in bucket_name/dir spanning all subdirectories. * gs://bucket_name/file*: matches files prefixed by file in bucket_name * gs://bucket_name/??.txt: matches files with two characters followed by .txt in bucket_name * gs://bucket_name/[aeiou].txt: matches files that contain a single vowel character followed by .txt in bucket_name * gs://bucket_name/[a-m].txt: matches files that contain a, b, … or m followed by .txt in bucket_name * gs://bucket_name/a//b: matches all files in bucket_name that match a//b pattern, such as a/c/b, a/d/b * gs://another_bucket/a.txt: matches gs://another_bucket/a.txt
SampleGcsFileSpecs List<EntryGcsFilesetSpecSampleGcsFileSpecArgs>: - Sample files contained in this fileset, not all files contained in this fileset are represented here. Structure is documented below.

FilePatterns []string: Patterns to identify a set of files in Google Cloud Storage. See Cloud Storage documentation for more information. Note that bucket wildcards are currently not supported. Examples of valid filePatterns: * gs://bucket_name/dir/*: matches all files within bucket_name/dir directory. * gs://bucket_name/dir/**: matches all files in bucket_name/dir spanning all subdirectories. * gs://bucket_name/file*: matches files prefixed by file in bucket_name * gs://bucket_name/??.txt: matches files with two characters followed by .txt in bucket_name * gs://bucket_name/[aeiou].txt: matches files that contain a single vowel character followed by .txt in bucket_name * gs://bucket_name/[a-m].txt: matches files that contain a, b, … or m followed by .txt in bucket_name * gs://bucket_name/a//b: matches all files in bucket_name that match a//b pattern, such as a/c/b, a/d/b * gs://another_bucket/a.txt: matches gs://another_bucket/a.txt
SampleGcsFileSpecs []EntryGcsFilesetSpecSampleGcsFileSpec: - Sample files contained in this fileset, not all files contained in this fileset are represented here. Structure is documented below.

filePatterns string[]: Patterns to identify a set of files in Google Cloud Storage. See Cloud Storage documentation for more information. Note that bucket wildcards are currently not supported. Examples of valid filePatterns: * gs://bucket_name/dir/*: matches all files within bucket_name/dir directory. * gs://bucket_name/dir/**: matches all files in bucket_name/dir spanning all subdirectories. * gs://bucket_name/file*: matches files prefixed by file in bucket_name * gs://bucket_name/??.txt: matches files with two characters followed by .txt in bucket_name * gs://bucket_name/[aeiou].txt: matches files that contain a single vowel character followed by .txt in bucket_name * gs://bucket_name/[a-m].txt: matches files that contain a, b, … or m followed by .txt in bucket_name * gs://bucket_name/a//b: matches all files in bucket_name that match a//b pattern, such as a/c/b, a/d/b * gs://another_bucket/a.txt: matches gs://another_bucket/a.txt
sampleGcsFileSpecs EntryGcsFilesetSpecSampleGcsFileSpec[]: - Sample files contained in this fileset, not all files contained in this fileset are represented here. Structure is documented below.

filePatterns List[str]: Patterns to identify a set of files in Google Cloud Storage. See Cloud Storage documentation for more information. Note that bucket wildcards are currently not supported. Examples of valid filePatterns: * gs://bucket_name/dir/*: matches all files within bucket_name/dir directory. * gs://bucket_name/dir/**: matches all files in bucket_name/dir spanning all subdirectories. * gs://bucket_name/file*: matches files prefixed by file in bucket_name * gs://bucket_name/??.txt: matches files with two characters followed by .txt in bucket_name * gs://bucket_name/[aeiou].txt: matches files that contain a single vowel character followed by .txt in bucket_name * gs://bucket_name/[a-m].txt: matches files that contain a, b, … or m followed by .txt in bucket_name * gs://bucket_name/a//b: matches all files in bucket_name that match a//b pattern, such as a/c/b, a/d/b * gs://another_bucket/a.txt: matches gs://another_bucket/a.txt
sampleGcsFileSpecs List[EntryGcsFilesetSpecSampleGcsFileSpec]: - Sample files contained in this fileset, not all files contained in this fileset are represented here. Structure is documented below.

EntryGcsFilesetSpecSampleGcsFileSpec

See the input and output API doc for this type.

FilePath string: - The full file path
SizeBytes int: - The size of the file, in bytes.

FilePath string: - The full file path
SizeBytes int: - The size of the file, in bytes.

filePath string: - The full file path
sizeBytes number: - The size of the file, in bytes.

filePath str: - The full file path
sizeBytes float: - The size of the file, in bytes.

Package Details

Repository: https://github.com/pulumi/pulumi-gcp
License: Apache-2.0
Notes: This Pulumi package is based on the google-beta Terraform Provider.

The Pulumi Platform

Get Started

Migrate to Pulumi

Solutions for All Teams and Engineers

Any Code

Any Cloud

Entry

Create a Entry Resource

Entry Resource Properties

Inputs

Outputs

Look up an Existing Entry Resource

Supporting Types

EntryBigqueryDateShardedSpec

EntryBigqueryTableSpec

EntryBigqueryTableSpecTableSpec

EntryBigqueryTableSpecViewSpec

EntryGcsFilesetSpec

EntryGcsFilesetSpecSampleGcsFileSpec

Package Details

On This Page