| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | |
| | | | |
| | | | |
| | | | | |
to forget the tests around the main find() method.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
been migrated over to the new organization. Where we
would have previously had an 'ldap' node terminus at
puppet/indirector/node/ldap.rb, we would not have it at
puppet/indirector/ldap/node.rb, and it would be a subclass
of puppet/indirector/ldap.rb.
These are called terminus classes, and there are now three
categories of them: The base class itself, abstract classes
that provide most of the functionality (e.g., the ldap and
yaml classes), and the classes themselves that implement
the functionality for a given model like Node or Facts.
The base terminus class handles auto-loading any of these
classes from disk.
|
| | | | |
| | | | |
| | | | |
| | | | | |
I only need to port the node indirection termini over.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
the indirection they're working with. It looks like I'll be
moving terminus registration to the indirection rather than the
top-level Indirector.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
and is tested, so now it is time to migrate the
Facts YAML Terminus to use the <terminus>/<indirection>
file structure instead of <indirection>/<terminus>.
In this case, that means that I am moving the functionality
in lib/puppet/indirector/facts/yaml.rb to
lib/puppet/indirector/yaml/facts.rb, and the class in that
new file will subclass Puppet::Indirector::Yaml.
|
| | | | |
| | | | |
| | | | |
| | | | | |
own file and adding a spec for it.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
terminus registration. I am about to change how loading is
handled, so that individual termini are declared as normal
Ruby classes.
|
| | | | |
| | | | |
| | | | |
| | | | | |
to add a few more specs, though.
|
| | | | |
| | | | |
| | | | |
| | | | | |
now work; all we need do is fix the indirector module tests.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
pass given the redesign that Rick implemented.
This was mostly a question of fixing
the method names and the mocks.
|
|\ \ \ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
calls out to the actual Terminus.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
instance_loader "utilities".
|
|\| | | | |
| |/ / / /
|/| | | | |
|
| | | | | |
|
|/ / / / |
|
| | | |
| | | |
| | | |
| | | | |
than the base PGraph class. I expect I will just do away with PGraph, but for now, I am at least going to keep configuration-related code in that class.
|
| | | |
| | | |
| | | |
| | | | |
generate a graph, rather than having to first convert to RAL types and then have them convert to a graph. This allows us to make it so components do not need a @children array at all. This was all done because I am having the "already a parent of" problem again, and I have gotten far enough that it is relatively easy to just make this problem go away once and for all.
|
| | | |
| | | |
| | | |
| | | | |
and are used instead of the network handlers, which have been removed. There are some failing tests as a result, but I want to get this code committed before I massage the rest of the system to make it work again.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
asked about, rather than when it is defined.
|
| | | |
| | | |
| | | |
| | | | |
indirector. I have not yet added the tests for the node handlers themselves, which is next.
|
|/ / / |
|
| |/
|/|
| |
| | |
autoload, which could class with Kernel.autoload.
|
|\ \ |
|
| | | |
|
| |\| |
|
| |\ \ |
|
| |\ \ \ |
|
| |\ \ \ \ |
|
| |\ \ \ \ \ |
|
| |_|_|_|_|/
|/| | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
problem was that the autoload tests were somehow clearing all loaded classes, including the providers. This is fixed now.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tests pass again, dammit.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
apparently broke this test.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
record that they were checked, so that they will be scheduled on the next run. This is a somewhat murky solution, but considering that no one had submitted this bug before, I expect it will not hit many people.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
but it is unfortunately disabled because we cannot realistically fix it using the current design. It will be easy after the REST refactor, though.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
qualified by prepending the wd to unqualified path names.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
parent classes can use tagged() to test if a node is a member of a subclass.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
used to be done.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
type, just like resource references do, which causes the resource and reference to again agree on the full name of a given defined type.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
I still do not really know how i will use it, though.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
keep any of this, but i wanted to store a copy before i got much further.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
instead of pre-extracting the configuration.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
again. This is the majority of the work necessary to make the separate "configuration" object work.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
that has a resource graph including resources for the container objects like classes and nodes. It is apparently functional, but I have not gone through all of the other tests to fix them yet. That is next.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
mostly just pointing directly to the compile, and I have begun (but commented out) the move to having resources to model each of the classes and nodes, in addition to the definitions. This will, again, enable a real Configuration object, and it will enable class versioning and similar features.
|