Tag is the Schema for the Tags API. Tags are used to attach custom metadata to Data Catalog resources.
Type
CRD
Group
datacatalog.gcp.upbound.io
Version
v1beta1
apiVersion: datacatalog.gcp.upbound.io/v1beta1
kind: Tag
TagSpec defines the desired state of Tag
No description provided.
This maps the ID of a tag field to the value of and additional information about that field. Valid field IDs are defined by the tag's template. A tag must have at least 1 field and at most 500 fields. Structure is documented below.
Reference to a Entry in datacatalog to populate parent.
Policies for referencing.
Selector for a Entry in datacatalog to populate parent.
Policies for selection.
Reference to a TagTemplate in datacatalog to populate template.
Policies for referencing.
Selector for a TagTemplate in datacatalog to populate template.
Policies for selection.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
This maps the ID of a tag field to the value of and additional information about that field. Valid field IDs are defined by the tag's template. A tag must have at least 1 field and at most 500 fields. Structure is documented below.
Reference to a Entry in datacatalog to populate parent.
Policies for referencing.
Selector for a Entry in datacatalog to populate parent.
Policies for selection.
Reference to a TagTemplate in datacatalog to populate template.
Policies for referencing.
Selector for a TagTemplate in datacatalog to populate template.
Policies for selection.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
TagStatus defines the observed state of Tag.
No description provided.
This maps the ID of a tag field to the value of and additional information about that field. Valid field IDs are defined by the tag's template. A tag must have at least 1 field and at most 500 fields. Structure is documented below.
Conditions of the resource.
basic-tag
apiVersion: datacatalog.gcp.upbound.io/v1beta1
kind: Tag
metadata:
annotations:
meta.upbound.io/example-id: datacatalog/v1beta1/tag
labels:
testing.upbound.io/example-name: basic_tag
name: basic-tag
spec:
forProvider:
fields:
- fieldName: source
stringValue: my-string
parentSelector:
matchLabels:
testing.upbound.io/example-name: entry
templateSelector:
matchLabels:
testing.upbound.io/example-name: basic_tag_template
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.