Github user overmeulen commented on the issue:
    Yes it would answer my use case. Actually I considered this option when 
doing the dev but I wasn't very fond of the Broker checking the whole tree of 
children nodes... I found it better to keep each node aware of just its direct 
children and it looked more correct to actually put the VirtualHostNode in 
ERRORed state too.


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to