dynamic sensors/rules

SUMMARY

Trying to find a way to implement dynamic sensors/rules

ISSUE TYPE

The kubernetes pack has a sensor that watches for the creation of third party resources (TPR - a type of resource within kubernetes that makes the api extensible). When a TPR is created, a new API endpoint is created within kubernetes, and the stackstorm kubernetes pack creates a new sensor to watch that endpoint.

When an instance of a TPR is created, we have a second pack thats specific to our platform that watches these new sensors via rules/triggers, and reacts to additions to them.

The problem lies in the ordering. When a trigger is fired, a rule should spot it. That rule needs to exist before the trigger is fired, otherwise it misses the event, and a sensor restart is required (after the rule has been created) to re-emit the trigger automatically.

So the question becomes how can I create a rule that kicks off a workflow based on a generated sensor, when the sensor doesn't exist when stackstorm is started?

Start with the Kubernetes pack's generated sensors and the rules/triggers that consume them, then trace how workflows are registered and how sensor events are emitted. The issue names no files or tests, so first clarify the intended lifecycle and ordering behavior with maintainers. Done means an agreed design and corresponding coverage for rules reacting to sensors created after startup.