Open b1conrad opened 3 years ago
Hm. Not as easy as I first thought. We know which pico requested the flush, but all picos with that same URL installed would need to receive the event. Probably we'll need to have the event percolate up to the root pico and then down through the children recursively.
So that a clever ruleset could keep track of its version in an entity variable. Then, when a flush happens that upgrades the version, a rule could migrate the other entity variables in some way.