| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|
|
|
| |
indirector. I have not yet added the tests for the node handlers themselves, which is next.
|
| |
|
|
|
|
| |
used to be done.
|
|
|
|
| |
instead of pre-extracting the configuration.
|
|
|
|
| |
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.
|
|
|
|
| |
resources to evaluate classes and nodes, not just definitions. This will hopefully simplify some of the parsing work, and it will enable the use of a Configuration object that more completely models a configuration.
|
|
|
|
| |
switch to git, and refactoring the evaluate_classes method on the compile object so I can use resources as intermediaries, thus making classes do late-binding evaluation.
|
| |
|
|
|
|
| |
life. This commit is mostly a bug-fix commit, resulting from the difference between real-life testing and unit testing.
|
| |
|
|
|
|
| |
especially WRT the environment.
|
|
|
|
| |
especially WRT the environment.
|
|
|
|
| |
piece to make this complete is to add multiple environment support to the fileserver. I also renamed Configuration.rb to Compile.rb (that is, I fixed all the classes that used to know it as a configuration).
|
|
|
|
| |
rspec
|
|
|
|
| |
transitional object and I want the real "configuration" object to be the thing that I pass from the server to the client; it will be a subclass of GRATR::Digraph.
|
|
|
|
| |
unit/ subdir
|
|
|
|
| |
Now I just need to go through the whole system and use the search path in addition to the parameter name itself.
|
|
|
|
| |
to manipulate it. All config tests pass in both the old tests and the new ones, so it is time to add the hooks for manipulating the search path.
|
|
|
|
| |
significantly changing its internals and the current tests, I think, will be harder to migrate than just writing rspec tests from scratch.
|
|
|
|
| |
environments, including the parser having an environment setting. I have also created my first spec-based tests, for the interpreter (and deleted the old test/unit tests).
|
|
|