Trigger
Run a flow as soon as files are uploaded to Azure Data Lake Storage
This trigger will poll the specified Azure Data Lake Storage bucket every interval. Using the from and regExp properties, you can define which files arrival will trigger the flow. Under the hood, we use the Azure Data Lake Storage API to list the files in a specified location and download them to the internal storage and process them with the declared action. You can use the action property to move or delete the files from the container after processing to avoid the trigger to be fired again for the same files during the next polling interval.
type: "io.kestra.plugin.azure.storage.adls.Trigger"Run a flow if one or more files arrived in the specified Azure Data Lake Storage bucket location. Then, process all files in a for-loop either sequentially or concurrently, depending on the concurrencyLimit property.
id: react_to_files
namespace: company.team
tasks:
- id: each
type: io.kestra.plugin.core.flow.ForEach
concurrencyLimit: 1
values: "{{ trigger.files | jq('.[].uri') }}"
tasks:
- id: return
type: io.kestra.plugin.core.debug.Return
format: "{{ taskrun.value }}"
triggers:
- id: watch
type: io.kestra.plugin.azure.storage.adls.Trigger
interval: PT5M
endpoint: "https://yourblob.blob.core.windows.net"
connectionString: "DefaultEndpointsProtocol=...=="
fileSystem: myFileSystem
directoryPath: yourDirectory/subdirectory
The action to perform on the retrieved files. If using NONE, make sure to handle the files inside your flow to avoid infinite triggering.
Connection string of the Storage Account.
The blob service endpoint.
Interval between polling.
The interval between 2 different polls of schedule, this can avoid to overload the remote system with too many calls. For most of the triggers that depend on external systems, a minimal interval must be at least PT30S. See ISO_8601 Durations for more information of available interval values.
The destination container and key.
The SAS token to use for authenticating requests.
This string should only be the query parameters (with or without a leading '?') and not a full URL.
List of execution states after which a trigger should be stopped (a.k.a. disabled).
The full destination directory path on the file system.
The destination file system.