| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Exporting or collecting resources no longer raises an exception
when no storeconfigs is enabled, it just produces a warning.
|
| |
|
|
|
|
| |
Also slightly modified the wording of some of the tests.
|
| |
|
|
|
|
| |
This is related to #1215.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
compile node configurations, rather than using the Configuration
handler, which was never used directly. I removed the Configuration
handler as a result.
Modified the 'master' handler (responsible for sending configurations
to clients) to always return Time.now as its compile date, so
configurations will always get recompiled.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
|
| |
stacked metaparameter values do not result in all resources
that receive a given default also getting those stacked
values.
|
|
|
|
|
| |
were getting finished multiple times, which meant they
got multiple copies of metaparams.
|
|
|
|
|
|
| |
in which statements are evaluated, which means that case
statements can now set variables that are used by other
variables.
|
|
|
|
| |
reparsing during a single run.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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).
|
| |
|
| |
|
| |
|
|
|
|
| |
tags in sql.
|
|
|
|
|
| |
including not compiling the configurations, and also storeconfigs
is no longer required during parse-testing.
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
*sworn* I did this weekend). In the process, I fixed
a couple of bugs related to differentiating between
nodes and classes, and then cleaned up quite a few
error messages.
|
| |
| |
| |
| | |
removing the bangs from 'add_vertex!' and 'add_edge!'.
|
| |
| |
| |
| |
| | |
since it's stupid to have a class named after
a verb.
|
| |
| |
| |
| |
| | |
and the AST::Node class to match that to
the definitions and AST classes.
|
| |
| |
| |
| |
| | |
be more internally consistent (switched store_resource
to add_resource, and store_override to add_override).
|
| |
| |
| |
| |
| |
| | |
refactored, fixing this problem and making the whole interplay
between the classes, definitions, and nodes, and the Compile class much
cleaner.
|
| |
| |
| |
| |
| | |
as its resource container, instead of having its own behaviour
around resource uniqueness.
|
| |
| |
| |
| |
| |
| | |
rspec, so I can refactor the class to more heavily rely
on a Node::Catalog instead of doing its own resource
container management.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
just returns a resource from its evaluate() method, and
all of the work is done in the evaluate_code method. This
makes the code cleaner, because it means 1) evaluate() has
the same prototype as all of the other AST classes,
2) evaluate() is no longer called indirectly through
the Parser Resource class, and 3) the classes themselves
are responsible for creating the resources, rather than
it being done in the Compile class.
|
| |
| |
| |
| |
| |
| | |
all of the evaluate() methods only ever accepted a scope,
and sometimes one other option, so I switched them all to
use named arguments instead of a hash.
|
| | |
|
| | |
|
|\ \ |
|
| |/
| |
| |
| | |
complain. This fixes #933
|
| |
| |
| |
| | |
longer ignored. (Cherry-picked from master.)
|
| |
| |
| |
| |
| |
| | |
classes for managing how the tokens work.
I also moved they tests to RSpec, but I didn't rewrite all of them.
|
|/ |
|
|
|
|
|
|
| |
the class parts are now added as tags. I've also
created a Tagging module that we should push throughout
the rest of the system that uses tags.
|
|
|
|
|
| |
bartv's, although I could not use his commit because it was
against the 'master' branch instead of 0.24.x.
|
|
|
|
| |
from the system, and implemented my own topsort method.
|
|
|
|
| |
times.
|
|
|
|
| |
against 0.24.0 servers.
|
|
|
|
|
|
| |
Hosts were keeping the export bit on all resources,
even when they'd collected another host's resources,
which caused a duplicate copy that was still exported.
|
| |
|
|
|
|
| |
host are no longer marked as not exported.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|