Hi,
if Puppet does not allow you to specify this preference, you could file
it as a feature request.
https://tickets.puppetlabs.com/
The Windows devs at PL are quite crafty, you might get a patch faster
than you think ;-)
Cheers,
Felix ( - throwing friends under the bus since 2013 )
On 03
On 23/03/16 21:04, Hunter Haugen wrote:
Given the resource you want to apply this pattern to, it can be turned
into a one-liner with a collector:
file { '/tmp/something':
ensure => file,
}
File['/tmp/something'] ~> Service <| title == 'apache2' |>
This means that if there is a service with a
On 23/03/16 21:56, Matt Zagrabelny wrote:
On Wed, Mar 23, 2016 at 3:04 PM, Hunter Haugen wrote:
Given the resource you want to apply this pattern to, it can be turned into
a one-liner with a collector:
file { '/tmp/something':
ensure => file,
}
File['/tmp/something'] ~> Service <| title ==
On Wed, Mar 23, 2016 at 3:04 PM, Hunter Haugen wrote:
> Given the resource you want to apply this pattern to, it can be turned into
> a one-liner with a collector:
>
> file { '/tmp/something':
> ensure => file,
> }
> File['/tmp/something'] ~> Service <| title == 'apache2' |>
Can you combine the
On Wed, Mar 23, 2016 at 3:04 PM, Hunter Haugen wrote:
> Given the resource you want to apply this pattern to, it can be turned into
> a one-liner with a collector:
>
> file { '/tmp/something':
> ensure => file,
> }
> File['/tmp/something'] ~> Service <| title == 'apache2' |>
>
> This means that
Given the resource you want to apply this pattern to, it can be turned into
a one-liner with a collector:
file { '/tmp/something':
ensure => file,
}
File['/tmp/something'] ~> Service <| title == 'apache2' |>
This means that if there is a service with a title of apache2 EVER added to
the catalog
Hello Gabriel,
The ticket that you reference has a link on it to a pull request which was
merged into Puppet 4.x.
https://github.com/puppetlabs/puppet/pull/3310
It is not intended that this will be fixed in Puppet 3.x.
As for deprecation, though it is a thorn in our side, removing support for
Greetings Puppet Users,
I have a chuck of code I'd like to centralize - you know DRY.
I've looked into a custom function, but I'm uncertain how to get at
the the puppet resources inside of ruby.
Here is the verbatim copy of the chuck in a puppet manifest:
if defined(Service['apache2']) {
$s
Puppet Server 2.3.1 is now available.
This is a bug-fix release that resolves a disruptive logging configuration
issue.
SERVER-1215 - If its Logback service is configured to log to syslog, Puppet
Server 2.3.0 fails to start. Puppet Server 2.3.1 fixes this regression,
which did not affect prior
Hello,
I'm trying to use the PE API to sign a server cert.
I know how to use /puppet-ca/v1/certificate_status but I have problems to
allow a specific user to sign.
I generated certs that I use in my curl/nodejs API calls and I have to
change the /etc/puppetlabs/puppetserver/conf.d/auth.conf. I
On Wed, Mar 23, 2016 at 5:19 AM <4nu...@gmail.com> wrote:
> Hi!
>
> Yes they enabled according to the guide. I forgot to tell. sorry!
>
> With the policy i found out that i need the arm-packages. Thats because i
> want to run it on raspberry pi.
>
> 500 http://apt.puppetlabs.com/ jessie/PC1 *armh
Luckily this doesn't happen all the time, but I've seen in twice now in
about a year's time on two different Puppet masters. Here's some
background.
I have in a central location a "Grand Master" that serves only the "Remote
Masters" each located in a different data center. On the remote masters
fact parsing was a problem with a template not the hiera code.
The only way I get this working is if I do a lookup in a profile manifest
of the main hash, then reference that variable back in hiera.
This seems wrong, and coupled, and flakey, which is why it's listed as a
bad practice on th
On 23/03/16 12:37, Martin Alfke wrote:
On 23 Mar 2016, at 12:23, Henrik Lindberg
wrote:
On 23/03/16 11:24, Martin Alfke wrote:
On 22 Mar 2016, at 22:53, Carthik Sharma wrote:
To answer the question in the subject, you're correct, as documented here for
Puppet 3.8
https://docs.puppetla
Hi!
Yes they enabled according to the guide. I forgot to tell. sorry!
With the policy i found out that i need the arm-packages. Thats because i
want to run it on raspberry pi.
500 http://apt.puppetlabs.com/ jessie/PC1 *armhf* Packages
release o=Puppetlabs,a=jessie,n=jessie,l=Puppetlabs,c=
On 23 Mar 2016, at 12:23, Henrik Lindberg
wrote:
> On 23/03/16 11:24, Martin Alfke wrote:
>>
>> On 22 Mar 2016, at 22:53, Carthik Sharma wrote:
>>
>>> To answer the question in the subject, you're correct, as documented here
>>> for Puppet 3.8
>>>
>>> https://docs.puppetlabs.com/puppet/3.8
On 23/03/16 11:24, Martin Alfke wrote:
On 22 Mar 2016, at 22:53, Carthik Sharma wrote:
To answer the question in the subject, you're correct, as documented here for
Puppet 3.8
https://docs.puppetlabs.com/puppet/3.8/reference/environments_classic.html#allowed-names
Is this only for Puppet
On 22 Mar 2016, at 22:53, Carthik Sharma wrote:
> To answer the question in the subject, you're correct, as documented here for
> Puppet 3.8
>
> https://docs.puppetlabs.com/puppet/3.8/reference/environments_classic.html#allowed-names
Is this only for Puppet 3.8 or is this also valid for Puppe
18 matches
Mail list logo