| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
| |
| |
| |
| | |
including removing some now-obsolete code and tests from
the Settings class.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
lib/puppet/node/catalog.rb
lib/puppet/type/pfile.rb
lib/puppet/type/pfilebucket.rb
lib/puppet/util/filetype.rb
spec/unit/node/catalog.rb
spec/unit/other/transbucket.rb
spec/unit/ral/provider/mount/parsed.rb
spec/unit/ral/types/file.rb
spec/unit/ral/types/interface.rb
spec/unit/ral/types/mount.rb
spec/unit/ral/types/package.rb
spec/unit/ral/types/schedule.rb
spec/unit/ral/types/service.rb
test/language/compile.rb
test/language/lexer.rb
test/language/snippets.rb
test/lib/puppettest.rb
test/ral/types/basic.rb
test/ral/types/cron.rb
test/ral/types/exec.rb
test/ral/types/file.rb
test/ral/types/file/target.rb
test/ral/types/filebucket.rb
test/ral/types/fileignoresource.rb
test/ral/types/filesources.rb
test/ral/types/group.rb
test/ral/types/host.rb
test/ral/types/parameter.rb
test/ral/types/sshkey.rb
test/ral/types/tidy.rb
test/ral/types/user.rb
test/ral/types/yumrepo.rb
|
| | |\|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
install.rb
lib/puppet/defaults.rb
man/man8/puppet.8
|
| | | |
| | |
| | |
| | |
| | | |
executable, since it otherwise causes caches to be used in all
cases, which we don't want (e.g., bin/puppet was using them).
|
| | | |
| | |
| | |
| | |
| | | |
server now that it's in the :puppetmasterd section rather than
a separate :yaml section.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
There is now a constant in Puppet::Network::HttpPool that will
disable or enable this feature, but note that we determined
that it can cause corruption, especially in file serving (but
it's client-side corruption).
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
date if the node facts have been updated (thus causing
node facts to again be available in manifests, for those
cases where they were not).
|
| | |\| |
|
| | | |
| | |
| | |
| | |
| | | |
circumstances (mostly, when loaded with other files, or
when loaded from rake or autotest rather than separately).
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, if there were an error creating a resource,
the error would propagate leaving any previously
created resources still in memory.
Now, resources are removed by default when an error
happens during instantiation, and the error propagates
to the caller so that they can log or whatever.
This also allows the Settings class to correctly and
separately handle the cases where we can't create the
catalog (which should never happen in normal usage but
was happening because of this error -- later catalogs
couldn't be created because earlier catalogs left
resources lying around) from those where we can't
apply the catalog.
|
| | | |
| | |
| | |
| | | |
once, which should make the system a bit more efficient.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
because they were conflicting with Puppet's autoloading.
This is clearly a sign that our autoloading is silly,
if Ruby's own loading easily makes it unhappy.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
(#1036). The problem only cropped up if there was a failure
when trying to manage the system -- this would cause the
setting-based resources not to get cleaned up.
|
| | | |
| | |
| | |
| | |
| | | |
as the version for a node, which should similarly encourage the
use of the yaml cache. (Related to #1130)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
cause ever-larger memory growth), and changing the external node
terminus to use the version of the facts as their version. This
will usually result in the cached node information being used,
instead of always hitting the external node app during file
serving. Note that if the facts aren't changed by the client,
then this will result in the cached node being used, but at this
point, the client always updates its facts. (#1130)
|
| | | |
| | |
| | |
| | | |
of the yaml file as the version of the object.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Note that this changes the behaviour a bit -- the resource's
noop setting always beats the global setting (previously,
whichever was true would win).
|
| | |\| |
|
| | | |\ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Replace the catalog with the newly created one when converting to ral types.
The aliases were being lost because the resources had references to the old catalog being converted
|
| | | | |
| | | |
| | | |
| | | | |
an environment and Puppet will now use it.
|
| | | | |
| | | |
| | | |
| | | | |
and the schema has been updated accordingly.
|
| | | |/
| | |
| | |
| | |
| | |
| | | |
stacked metaparameter values do not result in all resources
that receive a given default also getting those stacked
values.
|
| | |\| |
|
| | | |
| | |
| | |
| | | |
Some minor refactoring, pulling repeated setup up to 'before'
|
| | | |
| | |
| | |
| | | |
their tags are arrays.
|
| | | |
| | |
| | |
| | |
| | | |
were getting finished multiple times, which meant they
got multiple copies of metaparams.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
reparsing during a single run.
|
| | | |\ |
|
| | | | |\ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
with 0.24.x servers. :ignore links is now equivalent
to :manage links.
|
| | | | |/
| | |/|
| | | |
| | | |
| | | |
| | | | |
look resources up, which means there's no concern about
not finding the resource, which is where the nil was coming
from. We now just iterate over the vertices.
|
| | | | |
| | | |
| | | |
| | | | |
service types that need a control variable to enable/disable.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
some platforms (e.g., hpux) do not have a well-formed
requirement for the source.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
if the class had already been evaluated, but this was only
being run into in corner cases -- mostly where one class
included another class, I assume.
|
| | | |/
| | |
| | |
| | |
| | |
| | | |
resources whether they're isomorphic, and they in turn
ask the resource types (or default to true for defined
resource types).
|
| | |\| |
|
| | | |\ |
|
| | | | | |
|
| | | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
any objects, nor does it use Puppet's RAL resources. In the
process, I fixed #894 (you can now copy links) and refactored
other classes as necessary. Mostly it was fixing tests.
This is a squashed commit of a temporary branch, fwiw,
and it also includes any fixes to the tests that were
necessary to get all tests passing again.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
from the filesystem and failed when those keys
were unreadable.
|
| | | | |
|
| | | | |
|
| | |\|
| | |
| | |
| | |
| | |
| | | |
Conflicts:
CHANGELOG
|
| | | | |
|
| | | |\ |
|
| | | | | |
|
