Trigger jobs after objects are created or modified in a storage location
tilebox.workflows.automations.StorageEventTask
as your tasks base class instead of the regular tilebox.workflows.Task
.
all
method on the storage location client.
read
method on the storage client.
read
method instantiates a client for the specific storage location. This requires that
the storage location is accessible by a task runner and may require credentials for cloud storage
or physical/network access to a locally mounted file system.**
as a super-asterisk, a matching operator not sensitive to slash separators.Pattern | Matches |
---|---|
*.ext | Any file ending in .ext in the root directory |
**/*.ext | Any file ending in .ext in any subdirectory, but not in the root directory |
**.ext | Any file ending in .ext in any subdirectory, including the root directory |
folder/* | Any file directly in a folder subdirectory |
folder/** | Any file directly or recursively part of a folder subdirectory |
[a-z].txt | Matches a.txt , b.txt , etc. |
automations.delete
. After deletion, no new jobs will be submitted by the storage event trigger. Past jobs already triggered will still remain queued.
once
method.