I'm being a good boy and using the puppetdoc tool to document my
classes, however I'm hitting a minor annoyance.
The top level documentation for a module (let's call it "example) is
pulled from example/README (not example/manifests/init.pp), okay I can
cope with that.
The documentation for the cl
Posted 5mins too early, found the answer. Hopefully this will help
someone else.
# See example[link:classes/example/example.html]
HTH,
Adrian
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@go
It may also be worth looking at some form of improved scheduling in
order to avoid a thundering herd of requests to your puppetmasters.
One option that looks interesting (about to try it myself) is to use
mcollective:
http://www.devco.net/archives/2010/03/17/scheduling_puppet_with_mcollective.ph
Maybe I'm going a little nuts, this behaviour seems odd to me (and
inconsistent).
I have a puppet class like this:
class puppet::config {
File {
owner => "puppet",
notify => Service["puppet"],
}
file {
"/etc/puppet/puppet.conf":
content => template("puppet/puppet.conf"),
}
On Jan 17, 1:12 pm, Felix Frank
wrote:
[snip]
Hi Frank,
> I disbelieve that's how you are supposed to use this plusignment syntax.
> This is how I'm used to seeing it:
>
> class puppet::config {
> file { "foo": notify => Service["bar"] }
>
> }
>
> class puppet::config::server inherits puppet::
