Hi,
Is this the right place to report errors in the Puppet Learning Guide? I
have found a syntax error on page 57 while executing Task 2 of the
Variables and Class Parameters quest.
file { ${doc_root}/bonjour.html}
ensure = 'present',
content = em${french}/em,
}
Where is should be
file
On Nov 21, 2014, at 3:04 PM, Eric Sorenson eric.soren...@puppetlabs.com wrote:
On Wednesday, November 19, 2014 9:02:00 AM UTC-8, Tim.Mooney wrote:
Since RHEL 6.x has alternate versions of some packages (including ruby)
available via its Software Collections Library (SCL), I'm tempted
On Wednesday, November 19, 2014 11:02:00 AM UTC-6, Tim.Mooney wrote:
All-
For those of you that are using puppet on RHEL 6.x (/CentOS/Oracle
Linux/Scientific Linux/etc.) and have experienced ruby segfaults on
your puppet master(s), what workaround or workarounds have you been
using?
On Thursday, January 16, 2014 9:35:49 AM UTC-6, jyotir bhandari wrote:
Hi John
I just configured as you guided
[root@server manifests]# tree
.
|-- account
| `-- account.pp
|-- packages
| |-- ec2.pp
| |-- elinks.pp
| `-- nmap.pp
`-- site.pp
*accout.pp*
class user::add{
On Tuesday, October 15, 2013 8:08:10 AM UTC-5, jcbollinger wrote:
I'm not saying that categorically getting rid of ::params classes is a
viable target. In fact, I don't really understand why it was ever an
objective in the first place. On the other hand, I don't see why it makes
On Friday, October 11, 2013 7:12:32 PM UTC-5, Chuck wrote:
What would be nice but not necessary:
1) defined variable automatically have classname added to avoid global
conflicts.
eg.
Module: apache
variable: port
becomes global hiera: apache::port
+1
Defining a variable in
On Monday, September 23, 2013 10:02:18 AM UTC-5, Brandon Metcalf wrote:
OK, thanks. Based on the doc, it looks like if I have a host that acts as
a master and agent and the [master] and [agent] sections contain different
values for environment, then there is no way to get puppet config
This appears to be a bug. I've opened a ticket for resolution.
https://projects.puppetlabs.com/issues/19090
You can work around it by specifying the group in your user resource.
#puppet resource user logstash ensure=present gid=logstash
On Feb 5, 2013, at 10:01 AM, Abhijeet Rastogi
Hi,
I'm looking for a place to keep current on planned feature and big
fixes being included in Puppet Enterprise and the expected release
date.
I'm also curious if features are cherry picked from Puppet Community.
Example, feature 11044 is in Puppet Community 3.0.0. Do I have to
wait until PE
Hi,
I'm looking for a place to keep current on planned feature and big
fixes being included in Puppet Enterprise and the expected release
date.
I'm also curious if features are cherry picked from Puppet Community.
Example, feature 11044 is in Puppet Community 3.0.0. Do I have to
wait until PE
10 matches
Mail list logo
