I was using calling_class as an example. %{calling_module} used to work,
but now does not. Are you aware of what should be used instead? Things
like %{::hostname} do not work either.
My other real concern is that when using something like
"%{calling_module}/random_thing", there is no lookup for "/random_thing"
when calling_module is not interpolated as I would expect it to since it
should see it as a nil value.
On Tuesday, July 19, 2016 at 4:59:50 PM UTC-5, Gavin Williams wrote:
>
> John
>
> Yes, the 'common1' and 'common2' tiers are being ignored because
> 'calling_class' doesn't expand to anything when running on the command line.
>
> Try running
> hiera -d 'dhcpd::package_name' environment=production calling_class=*x*
> replacing x with the corresponding class_name you'd expect to be
> resolving...
>
> Gav
>
> On Tuesday, 19 July 2016 22:29:41 UTC+1, John Baird wrote:
>>
>> If you look at the hiera debug output from the last reply I posted, it
>> clearly shows that several folders with variables are not looked at when it
>> should be. Even if it doesn't find data in those folders, hiera should
>> still explicitly show that it is TRYING to look there, but that doesn't
>> happen. It clearly is not searching where it should be, which is why
>> everything is failing unless it's all hard-coded, which is obviously not
>> ideal.
>>
>> On Tuesday, July 19, 2016 at 2:16:10 AM UTC-5, John Baird wrote:
>>>
>>> Attempting to use hiera to hold all of my node-specific variables. It
>>> has been some time since I have run a puppet server, but I know it's not
>>> THAT hard. That being said, my modules run fine, but hiera is not looking
>>> them up correctly. It appears that any lines that contain any variables in
>>> the hiera.yaml are ignore and are not searched. Any assistance would be
>>> great! I'm sure it's something small, but sooooooo confused...
>>>
>>>
>>> HIERA.YAML
>>> ------------------
>>> ---
>>> :backends:
>>> - yaml
>>> :yaml:
>>> :datadir: "/opt/local/modules/hieradata"
>>> :hierarchy:
>>> - '%{calling_module}/%{::hostname}'
>>> - '%{calling_module}/common'
>>> - common
>>>
>>>
>>> hiera -d 'dhcpd::package_name' environment=production
>>> DEBUG: 2016-07-18 20:48:38 -0400: Hiera YAML backend starting
>>> DEBUG: 2016-07-18 20:48:38 -0400: Looking up dhcpd::package_name in YAML
>>> backend
>>> DEBUG: 2016-07-18 20:48:38 -0400: Looking for data source common
>>> DEBUG: 2016-07-18 20:48:38 -0400: Cannot find datafile
>>> /opt/local/modules/hieradata/common.yaml, skipping
>>> nil
>>>
>>>
>>> ---
>>> :backends:
>>> - yaml
>>> :yaml:
>>> :datadir: "/opt/local/modules/hieradata"
>>> :hierarchy:
>>> - '%{calling_module}/%{::hostname}'
>>> - '%{calling_module}/common'
>>> - common
>>> - puppet_test
>>>
>>> hiera -d 'dhcpd::package_name' environment=production
>>> DEBUG: 2016-07-18 20:49:30 -0400: Hiera YAML backend starting
>>> DEBUG: 2016-07-18 20:49:30 -0400: Looking up dhcpd::package_name in YAML
>>> backend
>>> DEBUG: 2016-07-18 20:49:30 -0400: Looking for data source common
>>> DEBUG: 2016-07-18 20:49:30 -0400: Cannot find datafile
>>> /opt/local/modules/hieradata/common.yaml, skipping
>>> DEBUG: 2016-07-18 20:49:30 -0400: Looking for data source puppet_test
>>> DEBUG: 2016-07-18 20:49:30 -0400: Cannot find datafile
>>> /opt/local/modules/hieradata/puppet_test.yaml, skipping
>>> nil
>>>
>>
--
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/096a7c43-6461-4f69-a9ee-d683fb71edb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
