> W.r.t interpolation of other hiera keys I have (perhaps surprisingly) > fewer issues. Since it is known at the start of evluation what is bound > to the respective keys and the designer of the data layout is > responsible for both keys there is really no problem (i.e. it is the > same concern). One naturally has to check for circularity, but that is a > small implementation detail. >
This has been our experience, that reasoning about hiera interpolation is actually easier than reasoning about scope lookups. Also, the addition of hiera interpolation support has allowed us to move more of our configuration data out of puppet node definitions and into hiera, which has allowed us to more clearly separate data from implementation as well as easily generate the yaml configuration files. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To post to this group, send email to puppet-dev@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
