On Thursday, 31 January 2019 12:48:30 UTC, Henrik Lindberg wrote:
>
>
> If you really must keep the CSV format, you can write your own function
> that you use with hiera 5. It is quite simple. I show examples and
> explain how hiera 5 works in this video:
>
> https://www.slideshare.net/PuppetL
On Wednesday, 30 January 2019 00:17:07 UTC, Ben Ford wrote:
>
> Your simplest and most straightforward upgrade path would be to port the
> CSV file to a common.yaml file and then switch to using lookup() with
> hieradata.
>
Thanks, Ben. That worked, and wasn't too painful.
Now all I have to
On 2019-01-30 01:16, Ben Ford wrote:
Your simplest and most straightforward upgrade path would be to port the
CSV file to a common.yaml file and then switch to using lookup() with
hieradata. Later on, you can start differentiating and build a sane data
hierarchy.
Check out the docs at https:/
Your simplest and most straightforward upgrade path would be to port the
CSV file to a common.yaml file and then switch to using lookup() with
hieradata. Later on, you can start differentiating and build a sane data
hierarchy.
Check out the docs at https://puppet.com/docs/puppet/latest/hiera_quick
I'm looking at the possibility of moving our Puppet manifests from 3.8 to
Something More Recent (i.e. 6.1)
We have one big CSV file for (mostly) encrypted passwords and the like.
And our existing manifests use extlookup to extract the relevant entries,
via calls like pw =
How should I replace
