I find it confusing that Puppet defines modules as reusable code yet,
when it comes to packages, you have to have prior knowledge of what
other package resources are defined.
Thank you for all the proposed solutions but does anyone know if
Puppet has a best practice they recommend in this case? Ot
You might want to change the regex used in the grep line to:
'^${user}:' # Adding the colon
This would prevent false-positives when, for e.g., you are looking for
user "joe" in a system where it doesn't exist but "joep" does.
On Feb 25, 5:19 pm, Romeo Theriault wrote:
> On Wed, Feb 22, 2012 at
I see that there's a thread from September asking a very similar
question ("Official puppetlabs position on cron vs puppet as a
service?"). I want to ask what should I take into account when making
this decision?
Just some background:
- All my servers are Red Hat or CentOS
- We have about 5 serve
You could use stages as described in documentation:
http://forge.puppetlabs.com/puppetlabs/firewall
On Dec 27, 1:48 am, Mark Walkom wrote:
> It's because puppet doesn't read sequentially but randomly accesses the
> module/class.
> You might be able to get around this by using a template.
>
> O
I'd reverse my stages if I were you. Seems like that will fix it.
On Dec 27 2011, 11:02 am, Jure Pečar wrote:
> On Tue, 27 Dec 2011 04:32:03 -0800 (PST)
>
> bel wrote:
> > You could use stages as described in documentation:
>
> >http://forge.puppetlabs.com/pup
I am working on this module:
https://github.com/belminf/puppet-iptables
I have this defined resource:
define iptables::hole ($proto='tcp', $port, $source=undef) {
firewall { "100 input: $name":
chain => 'INPUT',
proto => $proto,
dport => $port,
source => $source,
With regards to this line:
source => "puppet:///snmp/snmpd-($placement).conf",
I have two minor suggestions. First, it's probably neater to do this:
source => "puppet:///snmp/snmpd-${placement}.conf",
And then, for $placement = 'foo', the file would be:
modules/snmp/files/placement-foo.con
We have a database module and an application module that both require
gcc. When I include both modules in a node, I get errors about the
package being already defined.
How would I address this?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To
Thank you all. Updated the module and now works without the import:
https://github.com/belminf/puppet-iptables
On Jan 9, 8:51 am, jcbollinger wrote:
> On Jan 6, 9:10 pm, bel wrote:
>
>
>
>
>
>
>
>
>
> > I am working on this module:
>
> >https://gi
