Hi Andy, I guess my most important request for Hiera 2 is diagnostic information. It's probably a broader request for better diagnostics in puppet as a whole. Here's what I dream of ...
1. The ability to run Puppet on the puppetmaster using the cached Facts from a server. 2. A postmortem (sorry, retrospective) output that includes a dump of all internal variables. Probably a .yaml file. Ideally each variable should be able to state how it was set. Eg. Came from Hiera/qa_env/zookeeper_role/zabbix_module OR set at file:line module/zabbix/manifest/init.pp:136 To answer some questions about how we are using Hiera & more generally Puppet - we only use the yaml backend - we create custom facts for each server inside a puppet module (soon to be an ENC): location, project, role & server_env. The last could be renamed as server_collection or service_group. - Each Puppet Environment is a git clone of our repo. - Development activity is delivered into the tip and then we create a branch for the deployment pipeline: integration=>staging=>production. IMO, we need the branch because our puppet code is still young. When things are more stable we may be able to push straight from the tip. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
