DataTransferConfig is the Schema for the DataTransferConfigs API. Represents a data transfer configuration.
Type
CRD
Group
bigquery.gcp.upbound.io
Version
v1beta1
apiVersion: bigquery.gcp.upbound.io/v1beta1
kind: DataTransferConfig
DataTransferConfigSpec defines the desired state of DataTransferConfig
No description provided.
Reference to a Dataset in bigquery to populate destinationDatasetId.
Policies for referencing.
Selector for a Dataset in bigquery to populate destinationDatasetId.
Policies for selection.
Email notifications will be sent according to these preferences to the email address of the user who owns this transfer config. Structure is documented below.
Options customizing the data transfer schedule. Structure is documented below.
Different parameters are configured primarily using the the params field on this resource. This block contains the parameters which contain secrets or passwords so that they can be marked sensitive and hidden from plan output. The name of the field, eg: secret_access_key, will be the key in the params map in the api request. Credentials may not be specified in both locations and will cause an error. Changing from one location to a different credential configuration in the config will require an apply to update state. Structure is documented below.
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.
Reference to a Dataset in bigquery to populate destinationDatasetId.
Policies for referencing.
Selector for a Dataset in bigquery to populate destinationDatasetId.
Policies for selection.
Email notifications will be sent according to these preferences to the email address of the user who owns this transfer config. Structure is documented below.
Options customizing the data transfer schedule. Structure is documented below.
Different parameters are configured primarily using the the params field on this resource. This block contains the parameters which contain secrets or passwords so that they can be marked sensitive and hidden from plan output. The name of the field, eg: secret_access_key, will be the key in the params map in the api request. Credentials may not be specified in both locations and will cause an error. Changing from one location to a different credential configuration in the config will require an apply to update state. Structure is documented below.
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.
DataTransferConfigStatus defines the observed state of DataTransferConfig.
No description provided.
Email notifications will be sent according to these preferences to the email address of the user who owns this transfer config. Structure is documented below.
Options customizing the data transfer schedule. Structure is documented below.
Different parameters are configured primarily using the the params field on this resource. This block contains the parameters which contain secrets or passwords so that they can be marked sensitive and hidden from plan output. The name of the field, eg: secret_access_key, will be the key in the params map in the api request. Credentials may not be specified in both locations and will cause an error. Changing from one location to a different credential configuration in the config will require an apply to update state. Structure is documented below.
Conditions of the resource.
query-config
apiVersion: bigquery.gcp.upbound.io/v1beta1
kind: DataTransferConfig
metadata:
annotations:
meta.upbound.io/example-id: bigquery/v1beta1/datatransferconfig
labels:
testing.upbound.io/example-name: query_config
name: query-config
spec:
forProvider:
dataSourceId: scheduled_query
destinationDatasetIdSelector:
matchLabels:
testing.upbound.io/example-name: default
displayName: my-query
location: EU
params:
destination_table_name_template: my_table
query: SELECT name FROM tabl WHERE x = 'y'
write_disposition: WRITE_APPEND
schedule: first sunday of quarter 00:00
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.