| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
There is currently two type of documentation generation
for manifests (module or modulepath):
* RDoc HTML generation for modules and global manifests
* console output for sole manifest
Both version handles classes, defines, nodes, global
variable assignements, and resources when --all is used.
The usage is the following:
For the rdoc variant:
$ puppetdoc --mode rdoc --outputdir doc
It uses the puppet.conf configuration file to get the modulepath
and manifestdir settings. Those are overridable on the
command line with --modulepath and --manifestdir.
For the console output version:
$ puppetdoc /path/to/manifests
Signed-off-by: Brice Figureau <brice-puppet@daysofwonder.com>
|
|
which causes puppet to produce different exit codes depending
on whether there were changes or failures in the transaction.
Signed-off-by: Luke Kanies <luke@madstop.com>
|
|
|
|
|
|
|
|
|
|
Turns on the ICMP echo testing against the target host. Defaults to off.
111111111
|
|
The problem was that the mechanism I was using for
passing the node to the compiler was conflicting with
the Indirector::Request's method of handling node
authentication.
Signed-off-by: Luke Kanies <luke@madstop.com>
|
|
0.24.x
|
|
|
|
or reporting are enabled.
|
|
membership testing to the Ldap node terminus, and added tests,
|
|
|
|
Added environment awareness to --configprint
Pulled the logic for --configprint --genconfig and --genmanifest out of puppet.rb
Put the logic in lib/puppet/util/settings.rb and refactored it a bit
Added specs for the behavior
Reformated the whole spec file to use nested describe
Added the new method to the executables
The old behavior should be preserved, except for the env is now used
|
|
Add the class to handle certs, specs and modify puppetd
should fix 1190, 1199, 1200
|
|
|
|
|
|
|
|
|
|
|
|
executable, since it otherwise causes caches to be used in all
cases, which we don't want (e.g., bin/puppet was using them).
|
|
the setting of the loglevel and destination to just
one call, rather than the multiple calls that remained.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
including not compiling the configurations, and also storeconfigs
is no longer required during parse-testing.
|
|
reference), and adding error handling to puppetdoc.
|
|
correctly ignored, and you now use 'false' instead of 'none'
to explicitly ignore them.
|
|
|
|
|
|
caused other problems.
This whole thing will hopefully get *drastically* easier once we
get rid of global resources.
|
|
patch from #968.
|
|
certificate, and --verify, which uses the external openssl command to verify
the cert against the CA cert (I could not find an option to the builtin Ruby
libraries to do this).
|
|
a central module responsible for managing the http pool
(Puppet::Network::HttpPool), and it also handles
setting certificate information. This gets rid of
what were otherwise long chains of method calls,
and it makes the code paths much clearer.
|
|
|
|
set the 'node_terminus' setting to 'exec'.
|
|
wyvern's patch broke things a bit and I was stupid enough
not to run the tess right before accepting.
|
|
|
|
configuration file (it creates both default mount points
if it does) and puppetmasterd no longer requires the
configuration file to exist.
|
|
class for Parameter, which apparently lost the 'nodoc' method
for that class.
|
|
Previously, for example, the configuration terminus that was a
subclass of 'code' would have been stored at
lib/puppet/indirector/code/configuration and would have had
to have been named 'configuration'. Now, the subclass
can be named however the author prefers, and it must be stored
at lib/puppet/indirector/configuration/<name>.rb, where <name>
is the name you've chosen for the terminus type. The name only
matters insomuch as it is used to load the file from disk and
find the appropriate class when asked.
The additional restriction is that the class constant for the terminus
type must have its name as the last word, and the indirection must
be the second to last word. Thus, in our example, we can choose
any class constant that ends with Configuration::Code; given that
there's only one Configuration class at this point, it makes the
most sense to define the class as Puppet::Node::Configuration::Code.
This is somewhat awkward, because of the class's location on disk,
but the only other real option is to autogenerate a
Puppet::Indirector::Configuration class constant, which is, I think,
uglier.
|
|
|
|
This is the first real pass towards using caching. The `puppet`
executable actually uses the indirection work, instead of
handlers and such (and man! is it cleaner).
Most of this work was a result of trying to get the client-side
story working, with correct yaml caching of configurations, which
means this commit also covers converting configurations to yaml,
which was a much bigger PITA than it needed to be.
I still need to write integration tests, and I also need to cover
the server-side story of a normal configuration retrieval.
|
