Rudder

This is interesting.

I see three main problem before we can do that:

- it will be challenging to keep tracks of changes, b/c it means that we now have a graphe of node interdependencies;
- the graphe need to be directed, and so policy generation order becomes meaningful
- and I don't know how to deal with cycles.

So, we need to be able to build the directed dependency graphe not only for directive/rules but also for nodes and ensure it has nice properties (acyclic)

What about security, a property may be private to a node, we don't want to leak this information to another node

We don't have dependency between properties, so it's only checking that it is defined for that node (and checking that a node exists) and break policy generation if so

My main concern is more like benoit said, do we want to leak that information? I think we should only generate that value server side, not leaking it as a variable to the node directly.

We could still use a default value though