Package-level declarations
Types
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:
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:
Builder for EntryArgs.
An EntryGroup resource represents a logical grouping of zero or more Data Catalog Entry resources. To get more information about EntryGroup, see:
An EntryGroup resource represents a logical grouping of zero or more Data Catalog Entry resources. To get more information about EntryGroup, see:
Builder for EntryGroupArgs.
Three different resources help you manage your IAM policy for Data catalog EntryGroup. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Data catalog EntryGroup. Each of these resources serves a different use case:
Builder for EntryGroupIamBindingArgs.
Builder for EntryGroupIamBinding.
Three different resources help you manage your IAM policy for Data catalog EntryGroup. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Data catalog EntryGroup. Each of these resources serves a different use case:
Builder for EntryGroupIamMemberArgs.
Builder for EntryGroupIamMember.
Three different resources help you manage your IAM policy for Data catalog EntryGroup. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Data catalog EntryGroup. Each of these resources serves a different use case:
Builder for EntryGroupIamPolicyArgs.
Builder for EntryGroupIamPolicy.
Builder for EntryGroup.
Builder for Entry.
PolicyTag can be imported using any of these accepted formats
PolicyTag can be imported using any of these accepted formats
Builder for PolicyTagArgs.
For all import syntaxes, the "resource in question" can take any of the following forms* {{policy_tag}} Any variables not passed in the import command will be taken from the provider configuration. Data catalog policytag IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* {{policy_tag}} Any variables not passed in the import command will be taken from the provider configuration. Data catalog policytag IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for PolicyTagIamBindingArgs.
Builder for PolicyTagIamBinding.
For all import syntaxes, the "resource in question" can take any of the following forms* {{policy_tag}} Any variables not passed in the import command will be taken from the provider configuration. Data catalog policytag IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* {{policy_tag}} Any variables not passed in the import command will be taken from the provider configuration. Data catalog policytag IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for PolicyTagIamMemberArgs.
Builder for PolicyTagIamMember.
For all import syntaxes, the "resource in question" can take any of the following forms* {{policy_tag}} Any variables not passed in the import command will be taken from the provider configuration. Data catalog policytag IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* {{policy_tag}} Any variables not passed in the import command will be taken from the provider configuration. Data catalog policytag IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for PolicyTagIamPolicyArgs.
Builder for PolicyTagIamPolicy.
Builder for PolicyTag.
Tags are used to attach custom metadata to Data Catalog resources. Tags conform to the specifications within their tag template. See Data Catalog IAM for information on the permissions needed to create or view tags. To get more information about Tag, see:
Tags are used to attach custom metadata to Data Catalog resources. Tags conform to the specifications within their tag template. See Data Catalog IAM for information on the permissions needed to create or view tags. To get more information about Tag, see:
Builder for TagArgs.
Builder for Tag.
A tag template defines a tag, which can have one or more typed fields. The template is used to create and attach the tag to GCP resources. To get more information about TagTemplate, see:
A tag template defines a tag, which can have one or more typed fields. The template is used to create and attach the tag to GCP resources. To get more information about TagTemplate, see:
Builder for TagTemplateArgs.
Three different resources help you manage your IAM policy for Data catalog TagTemplate. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Data catalog TagTemplate. Each of these resources serves a different use case:
Builder for TagTemplateIamBindingArgs.
Builder for TagTemplateIamBinding.
Three different resources help you manage your IAM policy for Data catalog TagTemplate. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Data catalog TagTemplate. Each of these resources serves a different use case:
Builder for TagTemplateIamMemberArgs.
Builder for TagTemplateIamMember.
Three different resources help you manage your IAM policy for Data catalog TagTemplate. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Data catalog TagTemplate. Each of these resources serves a different use case:
Builder for TagTemplateIamPolicyArgs.
Builder for TagTemplateIamPolicy.
Builder for TagTemplate.
Taxonomy can be imported using any of these accepted formats
Taxonomy can be imported using any of these accepted formats
Builder for TaxonomyArgs.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/locations/{{region}}/taxonomies/{{taxonomy}} * {{project}}/{{region}}/{{taxonomy}} * {{region}}/{{taxonomy}} * {{taxonomy}} Any variables not passed in the import command will be taken from the provider configuration. Data catalog taxonomy IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/locations/{{region}}/taxonomies/{{taxonomy}} * {{project}}/{{region}}/{{taxonomy}} * {{region}}/{{taxonomy}} * {{taxonomy}} Any variables not passed in the import command will be taken from the provider configuration. Data catalog taxonomy IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for TaxonomyIamBindingArgs.
Builder for TaxonomyIamBinding.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/locations/{{region}}/taxonomies/{{taxonomy}} * {{project}}/{{region}}/{{taxonomy}} * {{region}}/{{taxonomy}} * {{taxonomy}} Any variables not passed in the import command will be taken from the provider configuration. Data catalog taxonomy IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/locations/{{region}}/taxonomies/{{taxonomy}} * {{project}}/{{region}}/{{taxonomy}} * {{region}}/{{taxonomy}} * {{taxonomy}} Any variables not passed in the import command will be taken from the provider configuration. Data catalog taxonomy IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for TaxonomyIamMemberArgs.
Builder for TaxonomyIamMember.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/locations/{{region}}/taxonomies/{{taxonomy}} * {{project}}/{{region}}/{{taxonomy}} * {{region}}/{{taxonomy}} * {{taxonomy}} Any variables not passed in the import command will be taken from the provider configuration. Data catalog taxonomy IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/locations/{{region}}/taxonomies/{{taxonomy}} * {{project}}/{{region}}/{{taxonomy}} * {{region}}/{{taxonomy}} * {{taxonomy}} Any variables not passed in the import command will be taken from the provider configuration. Data catalog taxonomy IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for TaxonomyIamPolicyArgs.
Builder for TaxonomyIamPolicy.
Builder for Taxonomy.