summaryrefslogtreecommitdiffstats
path: root/lib/puppet/defaults.rb
Commit message (Collapse)AuthorAgeFilesLines
...
| * Modified the 'factpath' setting to automatically configureLuke Kanies2008-05-161-3/+5
| | | | | | | | | | Facter to load facts there if a new enough version of Facter is used.
| * Added the ability to add arbitrary attributes to ldap.Gunnar Wrobel2008-05-151-0/+4
| | | | | | | | This fixes #1179.
* | The CRL is now automatically used or ignored.Luke Kanies2008-05-071-6/+2
| | | | | | | | | | | | | | | | | | Previously, you had to configure whether you wanted the CRL or not, which resulted in errors all the time when it was configured but unavailable. Now, Puppet will always create and try to use it, but you won't get failures if it's unavailable.
* | The master and client now successfully speak xmlrpc using the new system.Luke Kanies2008-05-071-9/+9
| | | | | | | | | | | | The server is actually serving REST, but the client can't use it until we resolve the format and security issues that REST hasn't yet tackled.
* | Moving some http configuration values to the mainLuke Kanies2008-05-051-14/+14
| | | | | | | | defaults section, rather than the puppetd section.
* | I think I've now got the Webrick SSL support working.Luke Kanies2008-04-281-1/+10
| | | | | | | | | | Now I just need to get xmlrpc working alongside REST in both mongrel and webrick.
* | Adding integration tests for a lot of the SSL code.Luke Kanies2008-04-171-1/+1
| | | | | | | | | | This flushed out some problems, and things mostly look good now, but I don't think we're quite there yet.
* | Changing all of the SSL terminus classes to treat CA files specially.Luke Kanies2008-04-171-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a kind of weird design situation. For instance, we've got a collection of certificates in the :certdir, but then there's a special CA certificate off by itself. Rather than build a whole separate infrastructure for managing those separate files (cert and key, at least), I decided to add special support for specifying where to find the CA-specific bits, and then code for handling them when necessary. This requires that we have a standard way of knowing whether we should be managing the CA bits or normal host files. The Puppet::SSL::Host class now has a 'ca_name' method that returns the string we're using for the CA name; this name is currently 'ca'. We have to use a name, because the name is the only thing that all methods have access to (e.g., when trying to 'find' the right cert, we only have the name available). What this means is that if you want access to the CA key or cert, then create a Puppet::SSL::Host instance with the name 'ca'. You'll still get the CA cert created with the host's :certname; it will just be stored in a different location.
* | Adding he last of the indirection classes for the sslLuke Kanies2008-04-151-0/+1
|/ | | | classes, finally including the certificate requests.
* Changing the default environment to production.Luke Kanies2008-04-081-1/+1
|
* Fixing #1138 -- the yamldir is automatically created by theLuke Kanies2008-03-241-6/+5
| | | | | server now that it's in the :puppetmasterd section rather than a separate :yaml section.
* Ported #198 man page creation functionality to 0.24.x branchJames Turnbull2008-03-221-3/+3
|
* Regression in :node_name functionalityJohn Ferlito2008-03-141-2/+2
| | | | When :node_name="cert" is specified the 'hostname' fact should be set to the SSL certificate common name instead of the results from facter. I've extended this to also set 'domain' and 'fqdn' since that makes a lot of sense to me. This fixes a regression introduced in SVN#1673
* Ticket #1041Andrew Shafer2008-03-051-0/+1
| | | | | | | | | | The CA serial file was getting owned by root because it was using a different method to write to file Pulled the readwritelock out of lib/puppet/sslcertificates/ca.rb into lib/puppet/util/settings.rb Refactored write, writesub and readwritelock a bit to reuse code (write and readwritelock both call writesub) Added a mode to :serial in lib/puppet/util/defaults.rb
* Fixing #1062 by moving the yamldir setting to its own yamlLuke Kanies2008-02-281-2/+5
| | | | | section. This should keep the yamldir from being created on clients.
* Applying patch by Jay to fix #989 -- missing crl files areLuke Kanies2008-02-071-1/+1
| | | | | correctly ignored, and you now use 'false' instead of 'none' to explicitly ignore them.
* Fixing #977 -- rundir is again set to 1777.Luke Kanies2008-01-191-1/+5
|
* Fixed ticket #979 - code configuration option docoJames Turnbull2008-01-011-1/+1
|
* Removing the ability to disable http-keep alive,Luke Kanies2007-12-191-2/+0
| | | | since it didn't work and is now unnecessary.
* Changing the statefile to only being managed by clients,Luke Kanies2007-12-121-7/+7
| | | | not by puppetmasterd.
* Renaming the 'null' terminus type to 'plain', asLuke Kanies2007-12-111-1/+1
| | | | requested in #960.
* Adding what is hopefully the last commit for #896. Here's theLuke Kanies2007-12-111-4/+3
| | | | | | | | | | | | | | changelog: Modifying the behaviour of the certdnsnames setting. It now defaults to an empty string, and will only be used if it is set to something else. If it is set, then the host's FQDN will also be added as an alias. The default behaviour is now to add 'puppet' and 'puppet.$domain' as DNS aliases when the name for the cert being signed is equal to the signing machine's name, which will only be the case for CA servers. This should result in servers always having the alias set up and no one else, but you can still override the aliases if you want.
* Fixing #951 -- external nodes work again, but you have toLuke Kanies2007-12-101-6/+3
| | | | set the 'node_terminus' setting to 'exec'.
* As per lutter; augmented fix for #896 to be configurable and defaulting to ↵Jeffrey J McCune2007-11-291-0/+3
| | | | validate the server certificate, honoring CVE-2007-5162.
* Merge branch 'plugins_mount', fixing #891.Luke Kanies2007-11-241-0/+1
|\ | | | | | | | | | | Conflicts: CHANGELOG
| * Integrating Matt Palmer's patch to provide a 'plugins'Luke Kanies2007-11-241-0/+1
| | | | | | | | | | | | | | | | | | | | 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.
* | Integrating most of Matt Palmer's fromLuke Kanies2007-11-241-0/+2
| | | | | | | | | | | | | | 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.
* | Adding patch ↵Luke Kanies2007-11-231-2/+1
|/ | | | 20070913010926-6856b-eb64be3b5169b7af674388124b406a1db7470880.patch from womble -- More restrictive permissions on some puppet-related directories
* Patching a bit for #804 by making the maximum much higher UIDLuke Kanies2007-11-231-1/+5
| | | | and making it tunable, but it has not gone away yet.
* Accepting a modified form of the patch from #885 by immerda.Luke Kanies2007-11-231-0/+2
|
* Applying patch from #896 by whaymond_home, adding moreLuke Kanies2007-11-231-2/+4
| | | | certname aliases.
* The Puppet settings instance now validates environments whenLuke Kanies2007-11-191-2/+4
| | | | you set an environment.
* Fixing #911 and #912 -- there's a default environment (development)Luke Kanies2007-11-191-4/+9
| | | | and you have to specify the valid environments for your site.
* Fixing #896 by applying DerekW's patches, with slightLuke Kanies2007-11-191-0/+2
| | | | modifications to fit coding style.
* fix dependency on $HOME, which causes massive failures when running without ↵David Schmitt2007-11-111-0/+4
| | | | | | environment lib/puppet/defaults.rb:10:in `expand_path': couldn't find HOME environment -- expanding `~/.puppet' (ArgumentError)
* Adding a :code setting for specifying code to runLuke Kanies2007-10-051-0/+3
| | | | | | | | instead of a manifest, and removing all of the ambiguity around whether an interpreter gets its own file specified or uses the central setting. Most of the changes are around fixing existing tests to use this new system.
* Switching the indirection from using settings for configurationLuke Kanies2007-10-041-9/+0
| | | | | | | | | | | | | | | to requiring explicit configuration. This means that if you as an application developer want to use a different indirection terminus then you have to specify it; something like: Puppet::Node.terminus_class = :ldap Caches use the same kind of configuration: Puppet::Node.cache_class = :memory Accordingly, I've removed the existing setting definitions from the defaults.rb.
* Merge branch 'master' of ssh://reductivelabs.com/opt/rl/git/puppetLuke Kanies2007-10-031-3/+6
|\ | | | | | | | | | | | | Conflicts: lib/puppet/defaults.rb lib/puppet/dsl.rb
| * Removing the Id tags from all of the filesLuke Kanies2007-10-031-1/+0
| |
| * Fixed #832. Added the '--no-daemonize' option to puppetd and puppetmasterd.Michael V. O'Brien2007-10-031-2/+6
| | | | | | | | | | The default behavior of 'verbose' and 'debug' no longer cause puppetd and puppetmasterd to not daemonize.
* | Fixing the yaml path so that it is correctlyLuke Kanies2007-10-031-6/+3
|/ | | | created for puppetmasterd.
* Adding my first integration test, verifying thatLuke Kanies2007-09-231-1/+3
| | | | | | | | | | | checksum interaction behaves as I expect when interacting with the file terminus. I've also changed how files and checksums behave a bit. Files now create model instances with the content as the only argument during initialization, and checksums now calculate their checksums rather than having them passed in.
* Renaming the 'Puppet::Util::Config' class toLuke Kanies2007-09-221-1/+1
| | | | | | | '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".
* Merge branch 'configurations' into indirectionLuke Kanies2007-09-221-2/+4
|\ | | | | | | | | | | | | | | | | Conflicts: lib/puppet/defaults.rb lib/puppet/indirector/facts/yaml.rb spec/unit/indirector/indirection.rb spec/unit/indirector/indirector.rb
| * The whole system now uses Configuration objects instead ofLuke Kanies2007-09-151-5/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ever converting the Transportable objects into a tree of components and then converting that into a graph. This is a significant step, and drastically simplifies the model of how to use a configuration. The old code might have looked something like this: file = Puppet::Type.create :path => "/whatever", ... comp = Puppet::Type.create :name => :whatever comp.push file transaction = comp.evaluate transaction.evaluate The new code looks like this: file = Puppet::Type.create :path => "/whatever", ... config = Puppet::Node::Configuration.new config.add_resource file config.apply I did not really intend to do this much refactoring, but I found I could not use a Configuration object to do work without refactoring a lot of the system. The primary problem was that the Client::Master and the Config classes determined how the transactions behaved; when I moved to using a Configuration, this distinction was lost, which meant that configurations were often needing to create other configurations, which resulted in a whole lot of infinite recursion (e.g., Config objects that create directories for Puppet use Configuration objects -- yes, I'm s/Config/Settings/g soon -- and these Configuration objects would need to create directories). Not everything is fixed, but it's very close. I am clearly over the hump, though, so I wanted to get a commit in.
* | All indirections are working, and they have allLuke Kanies2007-09-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | Adding the first top-level terminus (yaml). It worksLuke Kanies2007-09-211-3/+3
|/ | | | | | | | | | | 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.
* Doing an intermediate commit so rick can look at the work I have done so far.Luke Kanies2007-09-111-1/+1
|
* Renaming the file containing all of the configuration defaults to ↵Luke Kanies2007-08-281-0/+654
"defaults.rb", since I am going to create a separate "configuration" top-level directory to contain all of the classes related to managing the configuration for a given node.
generated by cgit (git 2.34.1) at 2025-09-27 05:21:30 +0000