summaryrefslogtreecommitdiffstats
path: root/ext/module_puppet
Commit message (Collapse)AuthorAgeFilesLines
* Removed some extraneous files from extJames Turnbull2009-12-021-209/+0
|
* Changed tabs to spaces without interfering with indentation or alignmentIan Taylor2009-06-061-6/+6
|
* Renaming Puppet::Node::Catalog to Puppet::Resource::CatalogLuke Kanies2008-12-181-1/+1
| | | | Signed-off-by: Luke Kanies <luke@madstop.com>
* Fixing puppet_module -- it needed the same node interface change.Luke Kanies2008-07-211-1/+1
| | | | | | I wonder if anyone's actually using this... Signed-off-by: Luke Kanies <luke@madstop.com>
* Adding changes to config print that were missed in fix for 1183Andrew Shafer2008-07-031-2/+3
|
* Fixing the executables to use the new indirection api.Luke Kanies2008-04-081-1/+1
|
* Renaming 'configuration' to 'catalog', fixing #954.Luke Kanies2007-12-111-3/+3
|
* Reorganizing the file structure for indirection terminus types.Luke Kanies2007-10-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Previously, for example, the configuration terminus that was a subclass of 'code' would have been stored at lib/puppet/indirector/code/configuration and would have had to have been named 'configuration'. Now, the subclass can be named however the author prefers, and it must be stored at lib/puppet/indirector/configuration/<name>.rb, where <name> is the name you've chosen for the terminus type. The name only matters insomuch as it is used to load the file from disk and find the appropriate class when asked. The additional restriction is that the class constant for the terminus type must have its name as the last word, and the indirection must be the second to last word. Thus, in our example, we can choose any class constant that ends with Configuration::Code; given that there's only one Configuration class at this point, it makes the most sense to define the class as Puppet::Node::Configuration::Code. This is somewhat awkward, because of the class's location on disk, but the only other real option is to autogenerate a Puppet::Indirector::Configuration class constant, which is, I think, uglier.
* All tests should now pass again.Luke Kanies2007-10-081-17/+26
| | | | | | | | | | | | | | This is the first real pass towards using caching. The `puppet` executable actually uses the indirection work, instead of handlers and such (and man! is it cleaner). Most of this work was a result of trying to get the client-side story working, with correct yaml caching of configurations, which means this commit also covers converting configurations to yaml, which was a much bigger PITA than it needed to be. I still need to write integration tests, and I also need to cover the server-side story of a normal configuration retrieval.
* Renaming the 'Puppet::Util::Config' class toLuke Kanies2007-09-221-3/+3
| | | | | | | 'Puppet::Util::Settings'. This is to clear up confusion caused by the fact that we now have a 'Configuration' class to model host configurations, or any set of resources as a "configuration".
* This is basically another intermediate commit. I feel likeLuke Kanies2007-09-171-2/+2
| | | | | | | | | | | | | | | | | | | | I've gone too far down the rabbit hole to turn back now, but the code is clearly getting more centralized around the Configuration class, which is the goal. Things are currently a bit muddy between recursion, dynamic resource generation, transactions, and the configuration, and I don't expect to be able to clear it up much until we rewrite all of the tests for the Transaction class, since that is when we'll actually be setting its behaviour. At this point, Files (which are currently the only resources that generate other resources) are responsible for adding their edges to the relationship graph. This puts them knowing more than I would like about how the relationship graph works, but it'll have to do for now. There are still failing tests, but files seem to work again. Now to go through the rest of the tests and make them work.
* Merging the webserver_portability branch from version 2182 to version 2258.luke2007-03-061-10/+10
| | | | git-svn-id: https://reductivelabs.com/svn/puppet/trunk@2259 980ebf18-57e1-0310-9a29-db15c13687c0
* Fixing module_puppet to use the usage? feature.luke2007-01-041-12/+4
| | | | git-svn-id: https://reductivelabs.com/svn/puppet/trunk@2042 980ebf18-57e1-0310-9a29-db15c13687c0
* Fixing puppetmodule to use env to find rubyluke2006-10-171-1/+1
| | | | git-svn-id: https://reductivelabs.com/svn/puppet/trunk@1798 980ebf18-57e1-0310-9a29-db15c13687c0
* adding -e ability to puppet executableluke2006-04-041-1/+1
| | | | git-svn-id: https://reductivelabs.com/svn/puppet/trunk@1065 980ebf18-57e1-0310-9a29-db15c13687c0
* Adding TERM to the signals being trappedluke2006-02-241-0/+14
| | | | git-svn-id: https://reductivelabs.com/svn/puppet/trunk@945 980ebf18-57e1-0310-9a29-db15c13687c0
* Change in how logging is defaulted: by default logs go to :syslog, unless ↵lutter2006-02-091-11/+10
| | | | | | the user explicitly gives at least one --logdest argument, in which case logs only go to the destinations the user gave. git-svn-id: https://reductivelabs.com/svn/puppet/trunk@895 980ebf18-57e1-0310-9a29-db15c13687c0
* There is now full support for configuration files, and the entire system has ↵luke2006-02-071-31/+30
| | | | | | been modified to expect their new behaviour. I have not yet run the test across all test hosts, though. git-svn-id: https://reductivelabs.com/svn/puppet/trunk@873 980ebf18-57e1-0310-9a29-db15c13687c0
* renaming the module, so it behaves better with people's svn clientsluke2006-01-041-0/+195
git-svn-id: https://reductivelabs.com/svn/puppet/trunk@773 980ebf18-57e1-0310-9a29-db15c13687c0
generated by cgit (git 2.34.1) at 2026-01-02 00:41:02 +0000