| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
| |
| |
| | |
during a run.
|
| | |
| |
| |
| |
| |
| |
| | |
caused other problems.
This whole thing will hopefully get *drastically* easier once we
get rid of global resources.
|
| | |
| |
| |
| | |
clear how to solve the problem.
|
| | |
| |
| |
| | |
managed resources.
|
| | |
| |
| |
| | |
since it didn't work and is now unnecessary.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| | |
a new connection is requested, and closing all connections
at the end of each run.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
While module specific plugins are a good thing, explicit plugins that don't fit into
modules should be allowed or at least not deprecated until it's proven that they are not
useful to anyone.
(Patch by Chris MacLeod.)
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | |/
|/|
| |
| | |
set the 'node_terminus' setting to 'exec'.
|
| |/
|
|
| |
validate the server certificate, honoring CVE-2007-5162.
|
| |
|
|
| |
a bit more useful.
|
| |
|
|
|
|
| |
configuration file (it creates both default mount points
if it does) and puppetmasterd no longer requires the
configuration file to exist.
|
| |\ |
|
| | |
| |
| |
| | |
connections.
|
| |\ \ |
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | |
| | | |
Conflicts:
CHANGELOG
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
mount, fixing #891. The patch was ported to the current
code by David Schmitt, I applied the rest of Matt's
patches, and I then fixed all of the code so that the
tests passed.
The primary change I had to make to the patch was reenabling
host expansion in paths -- his patch had disabled it.
|
| | | |
| | |
| | |
| | | |
related to providing a plugin mount.
|
| | |\ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is Matthew Palmer's work, from his debian package at
http://theshed.hezmatt.org/mattshacks/puppet/_patches/load_plugins_from_modules/20070831054902-6856b-0fd1481621def5d0c4d1ae48fb2f1dc357767c1e.patch
I just wriggled a few hunks so they apply.
|
| |\ \ \ \
| |_|_|/
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
http://theshed.hezmatt.org/mattshacks/puppet/_patches/puppet-0.23.2/.
There are still a few that haven't made it in, notably those related
to the plugins module, which I'm planning on integrating separately.
|
| | | | |
| | | |
| | | |
| | | | |
20071030035457-6856b-bd1c45ed5ecd753b2cb4f05347061f7245cc175a.patch from womble -- Force removal of directories during pluginsync
|
| | | | |
| | | |
| | | |
| | | | |
20070927050018-6856b-7fa134180aceb9cee2e667630345f5f8467a9d0c.patch from womble -- Catch more retryable errors in the XMLRPC call wrapper
|
| | | | |
| | | |
| | | |
| | | | |
20070927042000-6856b-38a0c82fd0a0d950937e7fe5a38b9901743402b3.patch from womble -- Recycle the connection more aggressively, to stop problems with clients that are newly requesting certificates
|
| | | | |
| | | |
| | | |
| | | | |
20070926235454-6856b-079fc12a9b63d59afd59aa205bc8bfeb350b097a.patch from womble -- Recycle the connection if we're presented with an EPIPE
|
| | |/ /
| | |
| | |
| | | |
20070905004837-6856b-2e7b8d8595ee0883537620c46424a4bf6174dc6a.patch from womble -- Add an attr_accessor for @http#ca_file, since older versions of libopenssl-ruby only provides ca_file=, not ca_file
|
| |/ /
| |
| |
| |
| | |
Master handler again; we need a better long-term solution,
though.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
resources. These are commits:
c19835ce9f8a5138b30a1a32ca741c996b0916d2
9290cc89a2206fb5204578f8e91208857a48b147
ffb4c2dbc7314b364d25e4f7be599ef05b767b44
|
| | | |
|
| |\ \ |
|
| | |/ |
|
| | |
| |
| |
| |
| |
| | |
At this point, I'm holding the experiment until after the release,
so I'm committing this for now and will take it back up after 0.24.0
is out.
|
| | |
| |
| |
| |
| | |
added to the configuration by the master client, rather than
by the creating types.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
references to resources. It deprecates the class-level
[] and []= methods, used for so long to provide closure
behaviour but now unnecessary with the node configuration's
ability to function as a resource container.
All of the spec tests pass, but there is much to do to make
the test/ tests pass, I expect.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
from the server. The real problem was getting all of the validation
done before any caching, which required a good bit more refactoring
than I expected.
In actuality, this commit is relatively small even though it covers
many files; most of the changes just make the code clearer or shorter.
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Puppet specs.
Created a spec/lib/monkey_patches/ directory for holding patches to RSpec functionality.
Extraced 'confine' and 'runnable?' support from the local copy of RSpec (spec/lib/spec/) and now load them from the monkey_patches/ directory.
Fixed a bad include in one of the specs.
Made it possible for the gem-installed spec binary (which autotest calls) to be used with Puppet.
Imported the Autotest::Rspec class, created a PuppetRspec autotest class, added a discovery.rb file for autotest to pick these up.
Autotest still has the following problems:
* it needs to be run with the proper include path:
% ruby -I spec/lib/ `which autotest`
* the patterns in our custom autotest handler (puppet_rspec) aren't yet fully specified (they
only recognize changes in our spec files, not changes in the puppet libs
which they are testing)
|
| | |
| |
| |
| | |
exception text is passed back via REST.
|
| | |
| |
| |
| | |
handlers. Refactor request building in REST handler specs.
|
| | | |
|
| | |\
| | |
| | |
| | |
| | |
| | | |
Conflicts:
spec/unit/indirector/indirection.rb
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Shouldn't "confine" produce some output when running spec? Who knows.
|