TriggerSchedule is the Schema for the TriggerSchedules API. Manages a Trigger Schedule inside a Azure Data Factory.
Type
CRD
Group
datafactory.azure.upbound.io
Version
v1beta1
apiVersion: datafactory.azure.upbound.io/v1beta1
kind: TriggerSchedule
TriggerScheduleSpec defines the desired state of TriggerSchedule
No description provided.
List of tags that can be used for describing the Data Factory Schedule Trigger.
Reference to a Factory in datafactory to populate dataFactoryId.
Policies for referencing.
Selector for a Factory in datafactory to populate dataFactoryId.
Policies for selection.
A pipeline block as defined below.
Reference to a Pipeline in datafactory to populate pipelineName.
Policies for referencing.
Selector for a Pipeline in datafactory to populate pipelineName.
Policies for selection.
A schedule block as defined below, which further specifies the recurrence schedule for the trigger. A schedule is capable of limiting or increasing the number of trigger executions specified by the frequency and interval properties.
Day(s) of the month on which the trigger is scheduled. This value can be specified with a monthly frequency only.
Days of the week on which the trigger is scheduled. This value can be specified only with a weekly frequency.
Hours of the day on which the trigger is scheduled.
Minutes of the hour on which the trigger is scheduled.
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.
List of tags that can be used for describing the Data Factory Schedule Trigger.
A pipeline block as defined below.
Reference to a Pipeline in datafactory to populate pipelineName.
Policies for referencing.
Selector for a Pipeline in datafactory to populate pipelineName.
Policies for selection.
A schedule block as defined below, which further specifies the recurrence schedule for the trigger. A schedule is capable of limiting or increasing the number of trigger executions specified by the frequency and interval properties.
Day(s) of the month on which the trigger is scheduled. This value can be specified with a monthly frequency only.
Days of the week on which the trigger is scheduled. This value can be specified only with a weekly frequency.
Hours of the day on which the trigger is scheduled.
Minutes of the hour on which the trigger is scheduled.
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.
TriggerScheduleStatus defines the observed state of TriggerSchedule.
No description provided.
List of tags that can be used for describing the Data Factory Schedule Trigger.
A pipeline block as defined below.
A schedule block as defined below, which further specifies the recurrence schedule for the trigger. A schedule is capable of limiting or increasing the number of trigger executions specified by the frequency and interval properties.
Day(s) of the month on which the trigger is scheduled. This value can be specified with a monthly frequency only.
Days of the week on which the trigger is scheduled. This value can be specified only with a weekly frequency.
Hours of the day on which the trigger is scheduled.
Minutes of the hour on which the trigger is scheduled.
Conditions of the resource.
tsexample
apiVersion: datafactory.azure.upbound.io/v1beta1
kind: TriggerSchedule
metadata:
annotations:
meta.upbound.io/example-id: datafactory/v1beta1/triggerschedule
labels:
testing.upbound.io/example-name: example
name: tsexample
spec:
forProvider:
dataFactoryIdSelector:
matchLabels:
testing.upbound.io/example-name: example
pipelineNameSelector:
matchLabels:
testing.upbound.io/example-name: example
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.