Deploy pipelines
In the SnapLogic Platform, tasks invoke pipelines and make them operational. After you design and test a pipeline locally, create a task to run it in production. Three types of tasks offer flexibility:
- Scheduled Tasks: Use this option to perform a job at a specific time or interval, or on a complex schedule.
- Triggered Tasks: Use this option to enable pipeline execution through an HTTP call. Triggered Tasks build a web API endpoint that allows data to be passed into and retrieved from a pipeline.
- Ultra Tasks: Use this option for specialized, low-latency jobs that need to process documents continuously. For low-latency jobs, a FeedMaster node in the Snaplex queues the incoming messages. The URL method is similar to triggered tasks, but the pipeline design limits specific Snaps. For Headless Ultra Tasks, which do not use a FeedMaster, the pipeline starts with a listening Snap that continuously polls or subscribes to an external data source, making the task preferable to a scheduled task.
Task authentication
| Task type | Basic Auth using Service Accounts | Bearer Token | JWT-based Access Control | API Policy Manager |
|---|---|---|---|---|
| Triggered Tasks |  |
|
|
|
| Ultra Tasks |  |
|
|
|
Triggered Tasks
Triggered Tasks support the following four authentication mechanisms:
- Basic Auth using Service Accounts: The simplest method, shared across tasks based on user ACLs, supporting password expiration.
- Bearer Token: Easy to use, with one unique token per task by default. Tokens can be manually synced across tasks.
- JWT-based Access Control: JWT Authentication implementation uses JWT Snaps in the pipeline for fine-grained access control at the project level or based on other criteria. JWT also allows for multiple tokens per task.
- API Policy Manager: Offers various authentication and authorization policies like Callout Authenticator and Generic OAuth policies.
Ultra Tasks
Ultra Tasks support the following three authentication mechanisms. Basic Auth using Service Accounts is not supported.
- Bearer Token: The default authentication method. Easy to use, with one unique token per task by default. Tokens can be manually synced across tasks.
- JWT-based Access Control: JWT Authentication implementation uses JWT Snaps in the pipeline for fine-grained access control at the project level or based on other criteria. JWT also allows for multiple tokens per task.
- API Policy Manager: Offers various authentication and authorization policies like Callout Authenticator and Generic OAuth policies.
Task permissions
SnapLogic tasks use the same permissions as other project assets. As an Environment admin, you can set the following permissions for other users at the project level:
- Read Only: View task configuration and details.
- Read & Write: View and modify tasks but can't run them.
- Read & Execute: View and run tasks but can't change configuration or details.
- Full Access: View, modify and run tasks.
- Owner: Modify permissions on the project that contains a task, in addition to all of the above.
If a user has different permissions at different levels, in general, the project permission level applies. For example, if you have Read & Execute permissions to the project space containing the task but only Read permissions to the project, you can't run the task. However, Full Access permission can't be overridden. If a user has Full Access to a project space, but read-only access to a specific project, they have full access to that project. If they have Full Access to a project but read-only to the project space, they have full access to that project.
Anyone with the bearer token can execute a Triggered or Ultra task. The task owner is the user who executes the pipeline when the task is invoked.
Task notifications
When creating or updating a task, you can configure email and Slack notifications based on status. For example, a task owner might enter themselves as a recipient and select "Stopped" as the event type. Environment admins can also create email and Slack notifications based on task duration. Configure task email and Slack notifications describes how to configure task notifications based on status and duration.