This is a hiera design i inherited -- each node can define a 'contextN' (1
through 6) in a contexts parameter in its hosts/${fqdn}.yaml, which is then
in the tree like:
contexts/.yaml
then the site.pp pulls in the 'contexts', sets $context1-6 and hiera uses
them as part of the lookup tree:
I believe that your hiera lookups won't be a problem. This is looking for
the usage of previously undefined variables more than the content of the
variables. If, however, it is truly undefined at that point due to some
ordering error, it seems like you'd want it to flag instead of be
I would be really cool if warnings could be disabled (And re enabled) from
code, like like pragmas in C++. That would let me keep the undefined
variables warning where it's needed, but ignore for other areas. (like
third party modules i may not care about)
In my case, i am using hiera lookup
On 02/15/2017 09:24 PM, Eric Sorenson wrote:
> That's great to hear François, thank you for testing the patch!
You are welcome. :)
> Our plan at
> this point is to accumulate a couple more fixes and ship a new build by
> Tuesday 21 Feb -
>
> I don't want to generate a new build containing
Hi Ryan,
Thank you for sharing this very useful info.
Did you ever try sending reports successfully from a standalone
PuppetMaster server to a Capsule which in turn was relayed back to the
Satellite?
Regards,
Suhail.
On Friday, 4 November 2016 20:42:56 UTC, Ryan Anderson wrote:
>
> One more
Hello folks,
I'm wondering if it is possible to define-declare a class. Something like
inlining:
instead of:
```
include hello_distro
That's great to hear François, thank you for testing the patch! Our plan at
this point is to accumulate a couple more fixes and ship a new build by
Tuesday 21 Feb -
I don't want to generate a new build containing only the fix in PUP-7215
because
(a) there is QA work underway on the current
Hey, it looks like everyone found this, but I wanted to add that we updated
this document with the hiera.yaml v5 format late last week, so if you were
looking for it outside of the google doc, it's up and running.
On 02/15/2017 05:44 PM, Moses Mendoza wrote:
> Thanks all for the reports. A fix is in progress / en route, trackable via
> https://tickets.puppetlabs.com/browse/PUP-7215
Ah ok, thanks Moses for the information.
I have tested in my testing VM and the commit of Thomas Hallgren seems
to work
Hi,
After some years of writing puppet modules, I think the ensure_resource
behaviour (from stdlib) should be the default behaviour for all resources.
This will simplify the code, and made Puppet more accessible for beginners.
Ref.
On Wed, Feb 15, 2017 at 06:47 Francois Lafont <
francois.lafont.1...@gmail.com> wrote:
> Oops, I have forgotten to say this:
>
> On 02/14/2017 08:51 PM, Daniel Urist wrote:
>
> > Just found this issue, which seems to describe what's going on:
> >
Oops, I have forgotten to say this:
On 02/14/2017 08:51 PM, Daniel Urist wrote:
> Just found this issue, which seems to describe what's going on:
> https://github.com/TomPoulton/hiera-eyaml/issues/222
> So eyaml is broken wrt hash merges? Are there any workarounds available?
Currently, the
Hi,
On 02/14/2017 08:51 PM, Daniel Urist wrote:
> Just found this issue, which seems to describe what's going on:
> https://github.com/TomPoulton/hiera-eyaml/issues/222
> So eyaml is broken wrt hash merges? Are there any workarounds available?
I have exactly the same problem here, and no
On 15/02/17 10:38, otheus uibk wrote:
> Hi Dom,
>
> The puppet documentation you references is just slight on details (well,
> that could be said about lots of projects these days).
If you're replying to a five year old thread(!), some context would be
handy. For reference:
Hi Dom,
The puppet documentation you references is just slight on details (well,
that could be said about lots of projects these days).
Does puppet put such lenses in its own directory? Does puppet ensure such
lenses override the "default" ones mentioned in the augtool page? All that
is
15 matches
Mail list logo
