Juan, facter is pretty much made for this very purpose. I actually like the way you've made use of it.
This data never needs to leave the local machine. Its just a local scratch pad, so putting it in ZK is a little bit weird.
What one needs to do is have a set of variables that are always accessible, which are controllable by each hook. I think this is a pretty common need, and will be used a lot with things like config settings.. where you may just store the settings in facts, and then re-run a common template regeneration mechanism. That sounds an awful lot like the way puppet does config management... and it also uses facter.
We should be able to develop a much lighter weight command that just stores keys/values locally and retrieves them when needed. I'd put this pretty low on the priority list though, as its not that terrible to depend on facter inside formulas.
Juan, facter is pretty much made for this very purpose. I actually like the way you've made use of it.
This data never needs to leave the local machine. Its just a local scratch pad, so putting it in ZK is a little bit weird.
What one needs to do is have a set of variables that are always accessible, which are controllable by each hook. I think this is a pretty common need, and will be used a lot with things like config settings.. where you may just store the settings in facts, and then re-run a common template regeneration mechanism. That sounds an awful lot like the way puppet does config management... and it also uses facter.
We should be able to develop a much lighter weight command that just stores keys/values locally and retrieves them when needed. I'd put this pretty low on the priority list though, as its not that terrible to depend on facter inside formulas.