On Thu, 29 Mar 2012 10:06:01 +0200
Martijn Grendelman <mart...@iphion.nl> wrote:
[...]
> >
> > ruby hashes are not stored in predictable order so this will
> > happen, the proposed solution should work.
> >
> > But as always the best is just to test it and see how it goes, it
> > wont bite :)
>
> <% aliases.sort_by {|key, value| key}.each do |key, val| -%>
>
> seems to do the trick. 'each_pair' doesn't work here, because the
> sort_by returns an array. Again, I learned something :-)
...and what about those of us which want the hash entries to appear in
the exact same order they are present in the puppet manifest? From what
I've seen, it was working that way up to 2.6 included, and only gets
"randomized" with puppet 2.7.
I've been doing things like this for a while now :
mm_cfg_settings => {
'ALLOW_SITE_ADMIN_COOKIES' => "Yes",
'PUBLIC_ARCHIVE_URL' => "'https://%(hostname)s/pipermail/%(listname)s'",
'MTA' => "'Postfix'",
'POSTFIX_STYLE_VIRTUAL_DOMAINS' => "'False'",
'DEFAULT_SUBJECT_PREFIX' => "''",
'DEFAULT_REPLY_GOES_TO_LIST' => "1",
},
<% mm_cfg_settings.each do |key,value| -%>
<%= key %> = <%= value %>
<% end -%>
In this particular example, order isn't critical other than for
readability, but I have some others where items must be in the same
order as they appear in the manifest's hash or things will break.
Is there a way to keep using hashes if the order from the manifest must
be kept in a file generated from the template?
Matthias
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
