UI for event driven notebook execution

[andrii-i]

Problem

Currently there is no way to trigger a notebook execution other than executing it manually or relying on job definition to execute it on schedule.

Proposed Solution

UI for event driven notebook execution. Trigger jobs based on S3 upload, etc. Define and reuse triggers.

[andrii-i]

Should users be able to define new trigger types, such as 's3 upload' or 'sql write', directly through the user interface? Or do we expect that defining new trigger types would be done programmatically only, and users would just use the UI to create triggers of those pre-defined types?

[andrii-i]

Should users be able to:

1. Just choose event type with associated parameters and values
2. Provide values for pre-determined parameters
3. Provide parameters and values at runtime

[simonaubertbd]

Hello @andrii-i

A thing I especially like is the scheduler on Qlik Sense :

There are two levels :
-the task
-the trigger

There can be several triggers for a task and different kind of trigger :
-time-based (like every day at 6 am)
-event-based (like if task 1 is ok and task 2 is ko). In this case there is a "time limit" for the time to wait.
(and of course y

Today, jupyter scheduler is ok for the first but the second would be more than great.

Best regards,

Simon