| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |\
| | |
| | |
| | | |
git://github.com/lak/puppet into 0.24.x
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
All requests should now have an ipaddress add to them, they
should always be marked authenticated or not, and they should
have the certificate name set as their 'node' if a certificate
is present.
They both use the same methods they use for xmlrpc,
although there's no common code, to facilitate deprecation
of xmlrpc.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This basically consists of the node name (i.e., the certificate name),
the IP, and whether the request is authenticated (which is determined
by whether it provided a valid certificate).
Now the two REST classes (mongrel and webrick) need to correctly
pass this information to the indirection calls they make.
|
| |/
| |
| |
| |
| |
| | |
(i.e., client-side templates). This would really only be used
for composite resources that pass the results of the template
on to generated resources.
|
| |
| |
| |
| |
| | |
Exporting or collecting resources no longer raises an exception
when no storeconfigs is enabled, it just produces a warning.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The Master handler previously provided the support for the :node_name
setting, and that functionality has now been moved into the Node
class. At the same time, the names to search through have been
changed somewhat: Previously, the certificate name and the
hostname were both used for searching, but now, the cert name
is always searched first (unless node_name == facter), but only
the Facter hostname, domain, and fqdn are used otherwise. We no
longer split the cert name, only the hostname/domain/fqdn.
In the general case, this provides no behaviour change, because
people's hostname is the same as their certname. This only
results in a change in behaviour if you specify a certificate
name that is a normal node name, and you want to look that node
up by something other than the full name in the certificate.
Signed-off-by: Luke Kanies <luke@madstop.com>
|
| |
| |
| |
| |
| |
| | |
This idiom is only functional when you have
Rails loaded, which is why it was failing for others
but not me.
|
| |
| |
| |
| |
| | |
I've set the default cadir and vardir to /dev/null, to
hopefully catch this kind of test sooner next time.
|
| |
| |
| |
| |
| | |
I was previously not clearing the cache using the Cacher.invalidate
method, which caused a test to fail.
|
| |
| |
| |
| | |
I just had to remove the '.clear' call.
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
CHANGELOG
lib/puppet/transaction.rb
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
master branch.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
catalogs.
It largely worked previously, except when aliases were set,
which require catalogs. This now converts all parser resources
to trans_objects then to RAL resources, and sets the catalog
in the meantime. This allows aliases to work just
fine when converting directly from parser catalogs to RAL catalogs.
|
| |
| |
| |
| |
| | |
Previously, they failed if you tried to get them to autogenerate
an id, because they assumed that a result would be returned.
|
| |
| |
| |
| |
| |
| | |
This renames the 'facter' confine to 'variable', and it prefers
settings to facts. There shouldn't really be any overlap, so
it shouldn't be a problem.
|
| | |
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
CHANGELOG
spec/integration/defaults.rb
spec/integration/node/catalog.rb
spec/unit/rails.rb
spec/unit/type/mount.rb
|
| | |
|
| |\ |
|
| | | |
|
| | |
| | |
| | |
| | | |
accessor for @@state to make testing a bit cleaner.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now each of the test types is a separate subclass
of Confine, so that they can have all of their own
logging and summarizing behaviour.
Also, added a 'feature' type, which can test for
the availability of Puppet features (and log
their absence more usefully).
|
| | |
| | |
| | |
| | |
| | | |
Facter to load facts there if a new enough version of
Facter is used.
|
| | |
| | |
| | |
| | |
| | | |
It mocked :exists? instead of :exist?, and my provider work
changed the method call because :exists? is going away in ruby.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I created a Confiner module for the Provider class methods,
and then I enhanced the interface between it and the Confine
class to make sure binary paths are searched for fresh each time.
This fixes #1197, which was a result of binary paths being
searched for at startup, rather than at execution.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This directory only existed as an organizational method,
and the code never matched it, so I'm fixing it.
|
| | |
| | |
| | |
| | | |
It was causing exceptions when run as part of the whole suite.
|
| |/
| |
| |
| | |
This fixes #1179.
|
| |
| |
| |
| | |
Also slightly modified the wording of some of the tests.
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
These providers use posixAccount and posixGroup.
This is a collapsed merge, fwiw.
|
| | | |
|
| |/ |
|
| |
| |
| |
| |
| | |
This provides a single, global bit for determining whether
a given piece of cached data is still valid.
|
| |
| |
| |
| |
| |
| |
| | |
I keep having issues with integration tests keeping
cached values around, and this module should hopefully
give us a single place to invalidate all caches, thus
making testing this much easier.
|
| |
| |
| |
| |
| |
| |
| | |
The HttpPool module now removes its cached ssl_host instance
when clearing its cache. This is really only useful
for testing, but it correctly causes the pool to use
new certificates when they're available.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, you had to configure whether you wanted the CRL or not,
which resulted in errors all the time when it was configured but
unavailable.
Now, Puppet will always create and try to use it, but you won't
get failures if it's unavailable.
|
| |
| |
| |
| |
| |
| | |
The server is actually serving REST, but the client can't use
it until we resolve the format and security issues that REST
hasn't yet tackled.
|
| |
| |
| |
| | |
class.
|