Set up sensor in terms of job, evaluate both sensor / job parameters.
Sensors are passed a hard-coded job definition. The external API evaluates the sensor definition and if successful, the resulting job run-time execution params.
prha on Oct 26 2020, 4:07 PM.Authored by
My major question is more high-level, in terms of our final ontology of Job, Schedule, Sensor, etc.
This proposal is thats SensorDefinition *contains* a job definition instance.
How does this relate to the ScheduleDefinition?
Did we consider a world where the Sensor *is a* job?
Wondering what the plan is here.
couple high-level questions to start, kinda related to nick's question