I was playing around with the new deep-merge hiera feature to check it's 
usability

I found some unexpected behaviour with array resolution

the following yaml files get parsed

top.yaml:
  ----
  arr:
    - 1
  hsh:
    arr:
      - 1

mid.yaml:
  ----
  arr:
    - 2
  hsh:
    arr:
      - 2

bot.yaml:
  ----
  arr:
    - 3
  hsh:
    arr:
      - 3

with :merge_behavior: deep (or deeper) I get the following result

$ hiera -a arr
[1, 2, 3]                     # I expected this

$ hiera -h hsh
{"arr"=>[3, 2, 1]}         # I expected {"arr"=>[1, 2, 3]}

I've located the curl-pit in the deep_merge gem, but I am not sure if this 
must be fixed there (the deep_merge gem is probably used by others)

any thoughts?

Fred.

-- 
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.


Reply via email to