Try command line.  Use the debug option
Dan White | d_e_wh...@icloud.com
------------------------------------------------
“Sometimes I think the surest sign that intelligent life exists elsewhere in the 
universe is that none of it has tried to contact us.”  (Bill Waterson: Calvin & 
Hobbes)

On Jun 03, 2016, at 03:03 PM, Leonard Smith <lrsm...@umich.edu> wrote:

Clarificaiton. I had tried in the hiera.yaml setting

:merge_behavior: deeper
 
the 
:merge_behavior: deep

and

:merge_behavior: native.

I unset it as well as from my understanding, from the documentation I am not 
concerned with deep merging. I just want to be able to specify two 
non-colliding 'vhosts' in two different YAML files and have both be created. 
The deep/deeper is only needed if the same key  exists and I want to merge the 
underlying key/values. 


On Friday, June 3, 2016 at 2:42:45 PM UTC-4, Leonard Smith wrote:
I've been trying to track down a problem with hiera_hash not merging.

puppet-3.8.6-1.el7
hiera-1.3.4-1.el7

## hiera.yaml
:hierarchy:
  - test
  - common

## test.yaml
---
rabbitmq_profile::vhosts:
  'test' :
    ensure: present

## common.yaml
---
rabbitmq_profile::vhosts:
  '/' :
    ensure: present

## rabbitmq_profile.pp

class rabbitmq_profile (

$vhosts = hiera_hash('rabbitmq_profile::vhosts',{})

) {

  notify { "<>$vhosts": }
  create_resources(rabbitmq_vhost, $vhosts )
}

## END


When I apply the manifest it creates the vhost specified in test.yaml but not 
the one in comon.yaml. I expected it to merge the has from both yamls and 
create the '/' and 'test' vhosts.

 If I remove test from hiera.yaml it creates the '/' vhost fine. I've tried 
setting the merge_behavior explicitly to native, deep and deeper, but I still 
see the behavior where it picks up the hash form the first yaml file it 
encounters and ignores the rest.



--
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/ad8306b9-a2ef-4d8b-8f2b-2f54196b6844%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/45e7dc49-245d-4d67-9ff4-028c67a95ec1%40me.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to