| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/
|
|
| |
and old client
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
there were enough problems fixing it that I decided something
more drastic needed to be done.
This uses the new Puppet::ResourceReference class to canonize
what a resource reference looks like and how to retrieve resources
via their references. Specifically, it guarantees that resource types
are always capitalized, even when they include '::' in them.
While many files are modified in this commit, the majority of changes are
quite small, and most of the changes are fixing the tests to use
capitalized types.
As we look at consolidating some of our resource types, we could consolidate
the ResourceReference stuff at the same time, but at least the
Puppet::Parser::ResourceReference class subclasses the main Puppet::ResourceReference
class.
|
|
|
|
| |
else can use to canonize how we refer to resources. Finally.
|
|
|
|
|
|
|
|
|
|
| |
what transportable resources get converted to, so
different names don't throw it off.
I also got rid of the Puppet::Type#merge method, which
has been deprecated for ages but was still in there. I
had to fix a few tests that weren't cleaning up after themselves
as a result.
|
|
|
|
| |
by rewriting the schedule tests entirely.
|
|
|
|
| |
after the test.
|
|
|
|
|
| |
rspec version. It's not perfect, in that it only tests
the :ensure state, but that's where 90% of the behaviour is.
|
| |
|
| |
|
|
|
|
|
|
| |
already migrated all of the tests into rspec but forgot about these
tests -- they were only in the rails/ subdir because people kept
not running the parser/ tests after modifying the Rails code.
|
|\
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
log level.
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
20071030034736-6856b-6004090b3968cdbf7d366a03ee1c44e2160a3fe0.patch
from womble, and rewriting and significantly enhancing the
unit tests for the Puppet::Parser::Collector class; it should
have full coverage now. There are no integration tests for
it, so there's still no guarantee that it works at all, but hey,
we're a lot better off than we were.
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
| |
20070913004017-6856b-cdbbba99de0b33b64874205a27833b5114fcc6b9.patch by womble -- Allow empty config settings
|
|
|
|
|
| |
longer uses the :target parameter (which I'll be removing in
the next commit).
|
|
|
|
|
| |
generate, rather than using ParsedFile. This should fix #777,
and has from what I can tell.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
being evaluated on the first pass because they were being
deleted from the collections list during evaluation, which caused
some to get skipped. This commit fixes that problem, which helps
in the trivial cases where the collections are in the same scope.
I expect it's still broken for more complicated usages.
|
|
|
|
| |
provider, since they are not needed
|
| |
|
|
|
|
|
|
| |
in #744 which broke the templates.
In the process, I also added test code for the redhat interface
provider and rewrote how parsing worked to make it more testable.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
rather than plenty of different places having the logic of how
to determine the default environment.
|
|
|
|
| |
you set an environment.
|
|
|
|
| |
and you have to specify the valid environments for your site.
|
|\ |
|
| |
| |
| |
| |
| | |
This option only writes the output of the command to the log if the command
failed.
|
| | |
|
| |
| |
| |
| |
| |
| | |
but only because the code (and my coding style, to some extent)
has changed so much in the last few months.
Also, added specs.
|
|\ \ |
|
| |/
| |
| |
| |
| | |
when running as root, examples trying to create directories
with non-standard users failed. This fix evades this difficulty.
|
| |
| |
| |
| |
| |
| |
| |
| | |
resources. These are commits:
c19835ce9f8a5138b30a1a32ca741c996b0916d2
9290cc89a2206fb5204578f8e91208857a48b147
ffb4c2dbc7314b364d25e4f7be599ef05b767b44
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Currently "Puppet::Type::File when used with replace=>false and content should
be insync if the file exists and the content is different" fails.
|
| |
| |
| |
| | |
on hashing.
|
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
switching the node scope to no longer be lazy evaluation,
just like I switched 'main'. When I made all of these
classes and nodes lazy evaluated, I should have decoupled
my real goal (using resources to evaluate them) from the idea
of lazy-evaluating them, and this basically does that.
I also changed the scope heirarchy slightly so that scopes will
tend to be below the node scope, altho this was already generally
the case.
|