On Thursday, July 23, 2015 at 9:01:42 PM UTC-5, Stack Kororā wrote:
>
>
>
> On Thursday, July 23, 2015 at 6:05:27 PM UTC-5, Ellison Marks wrote:
>>
>> No, the environment variable is set in the puppet.conf of every host. I'm
>> not even sure what the effect would be of trying to define environme
On Thursday, July 23, 2015 at 6:05:27 PM UTC-5, Ellison Marks wrote:
>
> No, the environment variable is set in the puppet.conf of every host. I'm
> not even sure what the effect would be of trying to define environment in
> hiera.
>
> Please see:
> https://docs.puppetlabs.com/puppet/latest/re
No, the environment variable is set in the puppet.conf of every host. I'm
not even sure what the effect would be of trying to define environment in
hiera.
Please see:
https://docs.puppetlabs.com/puppet/latest/reference/environments_assigning.html
On Thursday, July 23, 2015 at 3:21:27 PM UTC-7,
Greetings,
Thanks for the suggestions. I stepped out for a bit, but will try it as
soon as I get back.
On 07/23/2015 05:15 PM, Ellison Marks wrote:
> As far as I'm aware, in the default setup, there is no top level
> hieradata. as the comment says, the default datadir is
>
> /etc/puppetlabs/code
Ah, sorry, forgot the .yaml part of the filenames. hieradata would actually
look like this:
>
> /etc/puppetlabs/code/hieradata/
> common.yaml
> production/
> node1.example.com.yaml
> node2.example.com.yaml
> staging/
> node3.example.com.yaml
> dev/
> node4.example.com.yaml
As far as I'm aware, in the default setup, there is no top level hieradata.
as the comment says, the default datadir is
/etc/puppetlabs/code/environments/%{environment}/hieradata
So each environment will have it's own hieradata directory with it's own
common.yaml. /etc/puppetlabs/code/hieradata
