Hi all! Docs team here.
It looks like recursive Hiera data lookups were merged via pull request
152. However, we have no preliminary documentation for how this works and
what the limitations are -- across the multiple discussion threads and
multiple outdated implementations, it's looking like i
On Tue, Jul 2, 2013 at 3:27 PM, Eric Sorenson
wrote:
> - Reading through Wil's example is really interesting because it also
> touches on module reusability and module APIs. Are others on the thread in a
> similar situation, where you need to compose/abstract common config
> parameters to reduce
On Wednesday, July 3, 2013 5:06:36 PM UTC-5, Jesse Hathaway wrote:
> On Tuesday, July 2, 2013 5:27:56 PM UTC-5, Eric Sorenson wrote:
>
>> Hi Jesse -- I think this is getting pretty close, but you're right this
>> would not work without a major version bump. Some comments/questions from
>> the th
On Tuesday, July 2, 2013 5:27:56 PM UTC-5, Eric Sorenson wrote:
> Hi Jesse -- I think this is getting pretty close, but you're right this
> would not work without a major version bump. Some comments/questions from
> the thread--
>
> - The 'creeping perlism' of more sigils seems to be pretty unpo
On 3 July 2013 00:27, Eric Sorenson wrote:
> Hi Jesse -- I think this is getting pretty close, but you're right this
> would not work without a major version bump. Some comments/questions from
> the thread--
>
> - The 'creeping perlism' of more sigils seems to be pretty unpopular,
> instead most
Hi Jesse -- I think this is getting pretty close, but you're right this
would not work without a major version bump. Some comments/questions from
the thread--
- The 'creeping perlism' of more sigils seems to be pretty unpopular,
instead most people favour concrete syntax like your example below
If there are concerns with adding a new sigil '^', which is not obviously
intuitive, then I would propose keeping only one sigil for interpolation
'%' but being explicit on the type of lookup performed.
Examples:
1. Scope lookup of `potto01_ip`:
1. webserver_ip: "%{scope("potto01_ip")}"
+1 for the feature; I like Jeff's idea about using the existing sigil,
although I like Henrik's nested-function-like suggestion.
I think there is a particular case for this when it comes to lazy/busy
sysadmins integrating 3rd party modules from Puppet Forge (and for
encouraging writing internal mo
On 26 June 2013 17:29, Trevor Vaughan wrote:
> Something like % == scope and ^ == hiera? With the previous example:
> scope{potto01_ip} and hiera{potto01_ip}
>
And this fits nicely with the often proposed (and not yet accepted afaik)
facts hash.
facts['osfamily']
Dean
--
Dean Wilson
I've been following this discussion because I have also quickly hit the
point where I need to interpolate other hiera values.
Would it be possible to have % and ^ alias to a more descriptive
nomenclature?
Something like % == scope and ^ == hiera? With the previous example:
scope{potto01_ip} and h
>
>
>> I don't particularly like new syntax, but I do think it's possible to
> make this work without introducing more magic or more syntax.
>
> What if we just used the existing sigil and searched the hiera hierarchy
> before searching the Puppet scope? Would this address the magic and syntax
On Tue, Jun 25, 2013 at 6:06 PM, Eric Sorenson wrote:
> Hi, there's been a lively discussion on an interesting pull request that
> came in:
>
> https://github.com/puppetlabs/hiera/pull/137
>
> In the interest of soliciting input from a wider audience I'd like to move
> the discussion on this requ
On Wed, Jun 26, 2013 at 6:57 AM, Erik Dalén wrote:
>
> A big +1 from me for having the feature. I've needed it a couple of times,
> and the easiest workaround when not having it is simply data duplication,
> which is really bad.
> In some cases I've worked around that data duplication using more c
On 26 June 2013 03:06, Eric Sorenson wrote:
> Hi, there's been a lively discussion on an interesting pull request that
> came in:
>
> https://github.com/puppetlabs/hiera/pull/137
>
> In the interest of soliciting input from a wider audience I'd like to move
> the discussion on this request to the
Hi, there's been a lively discussion on an interesting pull request that came
in:
https://github.com/puppetlabs/hiera/pull/137
In the interest of soliciting input from a wider audience I'd like to move the
discussion on this request to the list.
Personally I have two issues, one major/semantic
15 matches
Mail list logo
