| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
a result of the move to no global resources.
|
|
|
|
|
| |
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
|
| | |
| | |
| | |
| | | |
Rakefile needs a rewrite
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
evaluation time, rather than resource instantiation time. This
means that you don't catch your "errors" as early, but it also
means you should be able to realistically configure a whole host
in one run.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
executable, since it otherwise causes caches to be used in all
cases, which we don't want (e.g., bin/puppet was using them).
|
| | |\ |
|
| | | | |
|
| | |/
| | |
| | |
| | |
| | |
| | | |
having it be a parameter. This is only useful if you want
a composite resource that just generates other resources and
passes the value on.
|
| | |
| | |
| | |
| | |
| | | |
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).
|
| | |
| | |
| | |
| | | |
matching. The actual problem was caused by the fix to #1001.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
any local variables and added a local variable -- see
http://snurl.com/21zf8. My own testing showed that this
caused memory growth to level off at a reasonable level.
Note that the link above says the problem is only with class
methods, but my own testing showed that it's any method that
meets these criteria. This is not a functional change, but
should hopefully be the last nail in the coffin of #1131.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
files, thanks to work by Adam Jacob and Arjuna Christenson
(the finding, not the leak). I'm going to act like this
fixes #1131, at least for now, but I doubt it does,
since that shows general memory growth over time, whereas
the leak here should go away as soon as files are reparsed
(because the parser is holding the reference to the leaking
array).
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
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).
|
| | |
| | |
| | |
| | | |
388cf7c3df7ce26e953949ed6fe63d76cbbb3691 to resolve #1137; also, add tests which detect the problem.
|
| | | |
|
| |\| |
|
| | |
| | |
| | |
| | | |
somewhat after commit 738d275f41f3eaf015800021dd2dfe6c42a1ae79, as promised.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
sophisticated about what we do at the beginning of the buffer, so that the first expression after an block-opening statement that happens to begin at the beginning of the buffer gets indented correctly. This may need some cleanup, but I wanted to get the correct behavior committed first.
Reported by: Micah Anderson
(Who again supplied the reproduction case.)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* puppet/ext/emacs/puppet-mode.el
(puppet-indent-line): When iterating backwards, test for
beginning-of-buffer first, to avoid an infinite loop.
Reported by: Micah Anderson
(He also supplied a clear reproduction recipe.)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
helper functions. (puppet-indent-line): Rewrite to handle three more situations: indent elements in an array, indent single-line blocks, and ignore previous comment content when indenting non-comment lines.
Suggested by: Micah Anderson
(He also provided the test data.)
Notes: Michah points out that this change may have introduced an
infinite loop (he can cause Emacs to hang now). Will investigate and
fix in a separate change.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
the setting of the loglevel and destination to just
one call, rather than the multiple calls that remained.
|
| | | |
|
| | |
| | |
| | |
| | | |
password management
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | | |
This was obsoleted in 0.24.2.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
(#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.
|
| | | |
|
| | | |
|