Thanks Eric, I didn't know that hiera would choose the file to apply after evaluating the variables in site.pp. That worked
On Sunday, February 2, 2014 8:37:04 AM UTC+1, Eric Sorenson wrote: > > This doesn't currently work, unfortunately. Hiera needs an update to > support that hash interpolation syntax. The bug tracking this is: > https://tickets.puppetlabs.com/browse/HI-14 > > it's slated for Hiera 1.4.0 but we don't have a specific release date > scheduled. As a workaround you can set a top scope variable in your site.pp > and use that for the hiera interpolation. > > --eric0 > > On Saturday, February 1, 2014 5:22:09 PM UTC+1, Carlos Sanchez wrote: >> >> Hi, >> >> I was trying to move a master using hiera with clientcert in the >> hierarchy to use the 3.4 $trusted["certname"] >> >> --- >> :backends: >> - yaml >> :yaml: >> :datadir: './hieradata' >> :hierarchy: >> - '%{::clientcert}' >> - '%{::custom_location}' >> - 'default' >> >> I tried to change %{::clientcert} to several options with no luck >> >> %{::trusted["certname"]} >> %{::trusted::certname} >> %{hiera("::trusted")["certname"]} >> >> In hiera I can see that %{::trusted} returns the hash a a string, but no >> idea how to access the individual key. What would be the correct syntax? >> >> Using 3.4.2 master and agent, hiera 1.3.1 and set trusted_node_data = >> true in puppet/conf >> >> Thanks >> >> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d791a664-71da-4ac9-869c-1f679d88c6f5%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
