Run boefje once at creation or update of ooi

[jpbruinsslot]

Dit boefje maar 1 keer draaien bij de create van een ooi, of eventueel als tweede spoor, dit boefje alleen draaien als het OOI veranderd. @underdarknl

From the scheduler we need to differentiate what types of boefje requires a different approach for calculating the next time a task needs to run or to run once. Likely we need to update the boefje definition in order to give the scheduler the necessary information on how to schedule the task.

[jpbruinsslot]

@underdarknl could you work out the requirements for this feature request and the likely scenarios?

[underdarknl]

@jpbruinsslot I agree we should add this as a flag to the boefjes definition if needed.
I propose the following options for a boefje:

• Interval (as already implemented, and the default scheduling strategy)
• Creation (indicated by a new flag in the boefjes definition runon: creation)
• Update (indicated by a new flag in the boefjes definition runon: update)

Deletion is never cause for a boefje to run, and neither are reads.
If the runon flag is present, the interval could be implemented as a delay, but I'd rather not overload that field, and instead just ignore it. We could present a warning to the user if both fields are set to explain the behavior for a given Boefje.

[underdarknl]

The likely usecase would be to run a boefje Once on every create/update to make sure we gather static data from a remote source, or send the OOI to a remote sink when we create/Update it in KAT. An alerting boefje that sends out the OOI 'as it happens' would be our first user of this feature.

[jpbruinsslot]

@underdarknl

So to recap:

• on a scan profile mutation event CREATE , or UPDATE and a boefje is NOT indicated to run once > a schedule should be created for this task such that this task will run more often
• on a scan profile mutation event CREATE and a boefje is indicated that is should only run once ONLY on creation for the ooi that this boefje can run on > the task should only be executed once and no schedule should be created
• on a scan profile mutation event UPDATE and a boefje is indicated that is should only run once ONLY on update for the ooi that this boefje can run on > the task should only be executed once and no schedule should be created

[jpbruinsslot]

mutation operation type	boefje runon	create schedule?	run task?
CREATE	["create"]	false	true
CREATE	["create", "update"]	false	true
CREATE	["update"]	false	false
CREATE	None	true	true
UPDATE	["create"]	false	false
UPDATE	["create", "update"]	false	true
UPDATE	["update"]	false	true
UPDATE	None	true	true

[jpbruinsslot]

PR #3906 is updated and can be tested with #3901

Note that tests haven't been written yet.

[jpbruinsslot]

Tests have been added to the PR