Hi Deo,
You have a typo in the file name. On disk it starts with W6Logon but in the
manifest it starts with W6Login.
Cheers,
Tim
On Fri, 10 May 2019, 03:05 Deo Breathnu, wrote:
> The file is there:
> -rw-rw-r-- 1 pe-puppet pe-puppet 1552 Apr 16 21:01 W6Logon.Service.Global
> [root@puppetmaste
Hi Gerardo,
Nice project!
A couple of things though, from someone who's been down this path before:
Developing against a moving target (i.e. the Puppet tokeniser) will end up
causing you a non-trivial amount of pain. The point where I decided to roll my
own tokeniser rather than use Puppet's (
Hi Dan,
Could you please file a bug report at https://github.com/rodjek/puppet-lint
including the manifest you used below?
Thanks,
Tim
On 19/04/2013, at 3:33 AM, Dan White wrote:
> I just tried it and the "fix" option does not.
>
> [root manifests]# puppet-lint -v
> Puppet-lint 0.4.0.pre1
>
Many of the speakers also put their slides on Speakerdeck and most people
include an email address and/or twitter handle in their slides. Just another
option.
Googling for their names might also return some results. Another option.
On Monday, 1 October 2012 at 2:15 PM, windowsrefund wrote:
Hi,
Why is it OK to have trailing whitespace in comments but not code?
On Thursday, 13 September 2012 at 4:43 AM, Antidot SAS wrote:
> Hi,
>
> I don't want to remove the error when it is accurate just when it is in a
> comment line, just asking not a big deal though...
>
>
>
> On Thu,
Hi,
-> and <- create ordering relationships (like the require and before
metaparameters)
~> and <~ create notify relationships (like the notify and subscribe
metaparameters)
You can read more about them at
http://docs.puppetlabs.com/puppet/2.7/reference/lang_relationships.html#chaining-arrows
Hi Peter,
Could I get you to file a bug report an
https://github.com/rodjek/puppet-lint/issues with all the relevant info?
Cheers,
Tim
On Thursday, 12 July 2012 at 12:11 AM, Peter Berghold wrote:
> Hi there,
>
> After seeing a tweet about puppet-lint I went ahead and installed puppet-li
Hi Markus,
For more information on what that script does, check out
http://rspec-puppet.com/setup/ (also contains a step by step guide for how to
setup rspec-puppet in your modules manually).
Cheers,
Tim
On Saturday, 26 May 2012 at 5:39 AM, Matthaus Litteken wrote:
> This is related to https:
So, rspec-puppet can't and won't ever work this way. What it's testing is the
resulting catalogue of Puppet resources that your host executes (the behaviour
of Puppet). Instead of testing that a variable is defined, you should be
testing the resource(s) that those variables control/adjust.
Fo
$user = $::operatingsystem ? {
/RedHat|CentOS/ => $::environment ? {
'production' => 'apache',
'dev' => 'nobody',
},
/Debian|Ubuntu/ => 'www-data',
}
On Wednesday, 11 April 2012 at 5:25 PM, Will S. G. wrote:
> Hi,
>
> I'm using one of the git projects for my Apache configuration
I believe you need to add "options => 'from="1.1.1.1"'" to your resource to do
this.
Cheers,
Tim
On Thursday, 29 March 2012 at 12:44 PM, Brandon wrote:
> Fairly new to puppet here and trying to figure out a couple of issues
> with distributing ssh keys. First one is how can I distribute a
> p
Run command if file exists:
exec { 'foo'
command => '',
onlyif => '/usr/bin/test -f /file/that/must/exist/for/exec/to/run',
}
Run command unless file exists
exec {
command => '',
creates => '/path/to/file',
}
On Tuesday, 13 March 2012 at 6:23 AM, Douglas Brancaglion wrote:
> Hi guys!
>
As Jeff said, ideally you wouldn't have any cross-module dependencies, but
everyone still does it.
There's a couple of ways you can solve this issue at the moment. The first
(and my preferred way) is to setup a fixtures directory as described in
http://bombasticmonkey.com/2012/03/02/automati
The only "clean" way to handle this that I can think of off the top of my head
is for Puppet to start silently discarding duplicate definitions and just using
the first one it comes across (with perhaps a message being logged at info
level so that it's not completely invisible).
This is far from i
You probably want your onlyif to look like
match command[./${name}='${value}'] size == 0
I would probably do something like this (https://gist.github.com/1619400). The
reason for the two augeas resources is one will create the command if it
doesn't exist at all, the other will update the name
I just use capistrano to do atomic updates of my manifest directory.
For those who haven't used capistrano, it checks out a new copy to
/releases/, symlinks it to /current (which is
where Puppet is configured to look) and then restarts the unicorns.
On 4 January 2011 13:35, Richard Crowley wrote:
Hi Luke,
I do something similar for a different module, give the following a try:
augeas { "mod_mkhomedir_for_pam_sshd":
context => "/files/etc/pam.d/sshd",
changes => ["ins 100 before *",
"set 100/type session",
"set 100/control require
Puppet logs to syslog so why not setup an alias that just runs "grep
puppet /var/log/messages". The log file may differ between
distributions (daemon.log for Debian), but this generally suffices for
me.
On 23 August 2010 00:20, Carl.caum wrote:
> You could always have a script that queries the p
18 matches
Mail list logo
