Option (2) allows you to test upgrades to the puppet infrastructure itself,
which changes not infrequently.
On Wed, Oct 11, 2017 at 3:15 PM, Antony Gelberg
wrote:
> I've asked a similar question on the Terraform mailing-list but on
> reflection, I think it's more appropriate here.
>
> Let's say
Thanks very much.
It would be great if the template doc page (
https://docs.puppet.com/puppet/5.3/lang_template.html) gave more guidance
on epp vs erp, use cases for each and possible gotchas like this.
On Fri, Oct 6, 2017 at 4:17 PM, Henrik Lindberg
wrote:
> On 06/10/17 11:28, Daniel Ur
I've noticed in classes with multiple templates that ERB variables seem to
share a single scope. That caught me by surprise-- is that intended
behavior?
Here's a simple test case:
class erb_scope_test (
)
{
$myarr1 = [ 'one' ]
$myarr2 = [ 'two' ]
$str1 = inline_template("<%= @myarr1.concat
I've written a simple custom service provider for monit that inherits from
the debian provider. Since this is running on debian systems, I want to use
the debian "enable" to enable/disable running at boot, but I want monit to
manage the running service rather than puppet.
Puppet::Type.type(:servic
Fixed by restarting puppetserver per
https://tickets.puppetlabs.com/browse/PUP-7337
It looks like the debian packages are missing a restart trigger:
https://tickets.puppetlabs.com/browse/PA-681
On Mon, Mar 13, 2017 at 11:10 AM, Daniel Urist wrote:
> I've tried replacing the
I've tried replacing the call to hiera_include() with a call to include()
like this (per
https://docs.puppet.com/puppet/latest/function.html#hierainclude) , but
that results in the same error:
include( lookup("roles::${role}", {'merge' => 'unique' }) )
On
So, this just started happening on all my nodes following upgrade to
puppet-agent 1.9.3-1jessie on my puppet master:
root@nweb8:/# puppet agent -t
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Loading facts
> Error: Could not retrieve catalog from remote server: Error 500 on SE
It turns out my issue was caused by eyaml no longer supporting deep hash
merges. I've worked around my issue by separating out plain yaml and eyaml.
Fortunately none of my existing code does a deep hash merge on the eyaml
keys.
It would be great to get some reassurance that eyaml will continue to
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?
On Tue, Feb 14, 2017 at 12:35 PM, Daniel Urist wrote:
> To get deep hash merges in hiera, I h
To get deep hash merges in hiera, I have been using the following in my
hiera.yaml:
> ---
> :merge_behavior: deeper
> :backends:
> - eyaml
And in one of my classes, a call to hiera_hash() like this:
$if_merged = hiera_hash('profiles::pserver::interfaces')
However, with puppetserver versio
I have been using ":merge_behavior: deeper" in my hiera.yaml file to turn
on deep hash merges with hiera_hash, but now this appears to be broken.
The latest docs (at https://docs.puppet.com/puppet/4.9/lookup_quick.html)
suggest using the lookup() function, but then state this:
IMPORTANT: These do
The release notes for puppetserver state the following (
https://docs.puppet.com/puppetserver/latest/release_notes.html):
Debian upgrade note: On Debian-based Linux distributions, logrotate will
> continue to attempt to manage your Puppet Server log files until
> /etc/logrotate.d/puppetserver is r
ng it today.
> Did you only see it with puppet runs against a master, or also with local
> puppet apply?
>
> On Fri, May 20, 2016 at 8:20 AM, Daniel Urist wrote:
>
>> I filed a bug: https://tickets.puppetlabs.com/browse/SERVER-1356
>>
>> On Fri, May 20, 2016 a
I filed a bug: https://tickets.puppetlabs.com/browse/SERVER-1356
On Fri, May 20, 2016 at 6:41 AM, JeremyCampbell
wrote:
> I can confirm the same issue on Puppetserver v2.4.0
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscrib
results in:
Notice: VAR1: VAR2: VAR3: VAR4: 'undef' VAR5: "undef"
On Thu, May 19, 2016 at 8:30 AM, Daniel Urist wrote:
> puppetserver: 2.3.2-1puppetlabs1
> puppet client: 3.8.5-2~bpo8+1
>
> Both server and clients are running Debian 8 (jessie); the pupp
>
> On Wed, May 18, 2016 at 2:33 PM, Daniel Urist wrote:
>
>> I have been using the yo61 logrotate module from puppetforge (
>> https://forge.puppet.com/yo61/logrotate), which seems to be the most
>> popular, but it recently stopped working, with many errors about undefin
I have been using the yo61 logrotate module from puppetforge (
https://forge.puppet.com/yo61/logrotate), which seems to be the most
popular, but it recently stopped working, with many errors about undefined
parameters.
The issue seems to be the use of the string 'undef' as a default value; for
exa
I've managed to solve this with query_resources() from puppedbquery to
generate an array of the resources and ensure_resource() to only create a
single instance. That seems to be the cleanest way at the moment to handle
this.
On Mon, Mar 7, 2016 at 9:25 AM, Ken Barber wrote:
> >> Model wise, in
I've created a module to configure a caching nginx proxy. I am running
several of these proxies behind a load balancer. They all proxy the same
external address. I'd like to export a nagios host/service for monitoring
the external address, which will then be collected on my nagios server. The
probl
Is there any update on when puppetdb will be available for Debian 8
(jessie)? Puppetserver is now available according to the announcement for
v.2.1.2.
On Wed, Oct 14, 2015 at 4:34 PM, Wyatt Alt wrote:
> PuppetDB 2.3.8 October 14, 2015
>
> PuppetDB 2.3.8 Downloads
>
>
>
Are there up-to-date instructions for how to install from the apt repos for
jessie?
On Fri, Jun 26, 2015 at 12:13 PM, Eric Sorenson <
eric.soren...@puppetlabs.com> wrote:
>
> Last night we rolled a patch release which includes a fix for FACT-1055, a
> regression which inadvertently broke backward
Is there any way to quote keys in hiera lookups so hiera doesn't interpret
periods as further lookups?
For example, if I have yaml that looks like this:
myservertype:
host1.domain:
somekey: somevalue
host2.domain:
somekey.somevalue
The periods in the keys host1.domain and host2.d
22 matches
Mail list logo
