Hi,
I've trying since the initial Facter 4 release to find information on how I can
use it - with Puppet, specifically. Is that documented anywhere? It would also
be useful to know what "the big deal" with Facter 4 is. This is also something
that was referenced in previous announcements here
Hi,
We just started our trials with puppet6 (upgrading from puppet5) on FreeBSD,
and while we think we have a pretty good grip on most things that we need to
do, there is one mind-bending problem we're having: When running the Puppet
Agent on the Puppetserver instance itself, it never prints
Ok I have _no_ idea how that happened. Sorry about the noise, folks!
/Eirik
> On 22 May 2019, at 16:05, Eirik Øverby wrote:
>
> Hei,
>
> jeg driver og roter i jailet nå - gi meg noen minutter!
> Er du på noen fornuftig IM-kanal som jeg kan bruke fra laptoppen min?
>
>
Hei,
jeg driver og roter i jailet nå - gi meg noen minutter!
Er du på noen fornuftig IM-kanal som jeg kan bruke fra laptoppen min?
/Eirik
> On 22 May 2019, at 15:52, samding dd wrote:
>
> Thank you for you reply.
>
> But how to get/build puppetserver on other platform than x86_64?
> The
> class foo:bar(
> $param1, # This enables you to provide 'param1' when instantiating
> the class,
> # and it enables auto-parameter-lookup for foo::bar::param1
> in Hiera.
> # if no value is given or found in Hiera, the value of
> $param1 will be
Hi,
> I don't fully understand Part 2: "2. You need any applicable resource-like
> declaration of class postgresql::server in the manifest set to not itself
> bind a value to the config_hash parameter."
You are probably declaring your class/resource setting default values for
parameters
On 8 Oct 2018, at 17:05, Henrik Lindberg wrote:
>
> On 2018-10-08 08:44, Eirik Øverby wrote:
>> Hi,
>> Sorry for hijacking this thread, but it caught my interest.
>> My scenario is that I'd like to re-use the title of an nginx server instance
>> in, say, the log
Hi,
Sorry for hijacking this thread, but it caught my interest.
My scenario is that I'd like to re-use the title of an nginx server instance
in, say, the log file for that server instance. However, since I don't want to
touch the nginx module itself, it seems I have to wrap its server class
> I would expect this to get into 5.5.7 but can't promise yet.
Brilliant - as long as it's not me being crazy. Thanks again.
/Eirik
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from
> Hi X,
>
> Nick Lewis helped me reproduce this issue with the extra module path, I have
> filed https://tickets.puppetlabs.com/browse/PUP-9211 for the issue.
>
> Thanks!
Thanks a *lot*!
I've resuscitated my JIRA account, so if you wish to attach me to the ticket in
some way, my username is
> Hi Eirik,
>
> I was unable to reproduce your issue in Puppet 5.5.6 (aka SHA 60de165 from
> https://github.com/puppetlabs/puppet/releases):
>
> kris.bosland@kris:puppet % git checkout 60de165
>
On Tuesday, August 28, 2018 at 6:50:48 PM UTC+3, Branan Purvine-Riley wrote:
> Hi Jon,
>
> In Puppet 6 we're going to start requiring that the names of
> classes/defines match the name that's implied by their file path[1]. We
> added that deprecation warning in 5.5.6[2] as part of a push to get
12 matches
Mail list logo
