summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* | Moving Parameter utility classes into separate filesLuke Kanies2010-02-176-454/+471
| | | | | | | | Signed-off-by: Luke Kanies <luke@madstop.com>
* | Switching transactions to callback-based eventsLuke Kanies2010-02-177-367/+593
| | | | | | | | | | | | | | | | | | | | | | | | | | Events are now queued as they are created, and the queues are managed through simple interfaces, rather than collecting events over time and responding to them inline. This drastically simplifies event management, and will make moving it to a separate system essentially trivial. Signed-off-by: Luke Kanies <luke@madstop.com>
* | removing never-used codeLuke Kanies2010-02-171-61/+0
| | | | | | | | Signed-off-by: Luke Kanies <luke@madstop.com>
* | Moving log destination code into separate filesLuke Kanies2010-02-173-276/+281
| | | | | | | | Signed-off-by: Luke Kanies <luke@madstop.com>
* | fixed a couple of typosMarc Fournier2010-02-172-2/+2
| |
* | Unit tests for path changesMarc Fournier2010-02-171-0/+14
| |
* | Handle path elements with ticks and spacesBryan Kearney2010-02-171-2/+8
| |
* | Fix builtins glob in single executableRein Henrichs2010-02-171-1/+2
| |
* | Fix failing specsRein Henrichs2010-02-175-15/+15
| | | | | | | | Some variable ns were missed in the rename
* | Rename puppet application spec to mainRein Henrichs2010-02-171-74/+74
| |
* | Renaming the old puppet executableRein Henrichs2010-02-172-3/+3
| |
* | Find both bin and sbin usage docs, fail gracefullyRein Henrichs2010-02-171-3/+6
| |
* | Fix application name in bin/ralshRein Henrichs2010-02-171-1/+1
| |
* | Initial puppet single executableRein Henrichs2010-02-172-2/+29
| | | | | | | | | | | | | | - puppet executable delegates to available applications and provides basic usage information - Puppet::Application.applications accessor added for access by main executable - Ugly hack to make RDoc::usage work
* | Renaming applications, mostly removing 'puppet'Luke Kanies2010-02-1720-381/+384
| | | | | | | | Signed-off-by: Luke Kanies <luke@madstop.com>
* | Some tests were leaking state when the test failedJesse Wolfe2010-02-172-2/+7
| |
* | Typo in method call in test.Jesse Wolfe2010-02-171-1/+1
| |
* | Supressing warnings (not really failures) in test/unitJesse Wolfe2010-02-172-9/+19
| |
* | Fix test using wrong Puppet util filesetting groupRein Henrichs2010-02-171-1/+1
| |
* | Mock user in SUIDManager testsRein Henrichs2010-02-171-2/+7
| |
* | Removing resources generate testsRein Henrichs2010-02-171-78/+0
| | | | | | | | | | | | Tests that generating resources performs a check and only returns resources that check as true. There is already spec coverage for this behavior.
* | Removing old test for service/debian providerRein Henrichs2010-02-171-58/+0
| | | | | | | | it has been superceded by an rspec spec.
* | Replace test/unit file write test with specRein Henrichs2010-02-172-32/+36
| |
* | Allow adding single key to hashesBrice Figureau2010-02-176-901/+1007
| | | | | | | | | | | | | | | | | | | | This patch allow this syntax: $hash[mykey] = 12 If the key already exist an error is raised. Hashes are essentially write only, like puppet variables. Signed-off-by: Brice Figureau <brice-puppet@daysofwonder.com>
* | Raise an error when appending not a hash to a hashBrice Figureau2010-02-172-4/+10
| | | | | | | | Signed-off-by: Brice Figureau <brice-puppet@daysofwonder.com>
* | Fix #2389 - Enhance Puppet DSL with HashesBrice Figureau2010-02-1711-918/+1389
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This bring a new container syntax to the Puppet DSL: hashes. Hashes are defined like Ruby Hash: { key1 => val1, ... } Hash keys are strings, but hash values can be any possible right values admitted in Puppet DSL (ie function call, variables access...) Currently it is possible: 1) to assign hashes to variable $myhash = { key1 => "myval", key2 => $b } 2) to access hash members (recursively) from a variable containing a hash (works for array too): $myhash = { key => { subkey => "b" }} notice($myhash[key][subjey]] 3) to use hash member access as resource title 4) to use hash in default definition parameter or resource parameter if the type supports it (known for the moment). It is not possible to string interpolate an hash access. If it proves to be an issue it can be added or work-arounded with a string concatenation operator easily. It is not possible to use an hash as a resource title. This might be possible once we support compound resource title. Unlike the proposed syntax in the ticket it is not possible to assign individual hash member (mostly to respect write once nature of variable in puppet). Signed-off-by: Brice Figureau <brice-puppet@daysofwonder.com>
* | Fix #2929 - Allow checksum to be "none"Brice Figureau2010-02-1710-5/+76
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | File checksum is "md5" by default. When managing local files (not sourced or content) it might be desirable to not checksum files, especially when managing deep hierarchies containing many files. This patch allows to write such manifests: file { "/path/to/deep/hierarchy": owner => brice, recurse => true, checksum => none } Then puppet(d) won't checksum those files, just manage their ownership. Signed-off-by: Brice Figureau <brice-puppet@daysofwonder.com>
* | Fix #3186 - require function set relationship only on the last classBrice Figureau2010-02-173-4/+31
| | | | | | | | | | | | | | | | Due to the fact that resource.set_parameter is overwriting the previous set_parameters, we were losing the previous relationships we set there, either in a previous call of require or in the same call. Signed-off-by: Brice Figureau <brice-puppet@daysofwonder.com>
* | Fixing #3185 Rakefile is loading puppet.rb twiceJesse Wolfe2010-02-171-1/+1
| | | | | | | | | | | | | | A 'require' statement with a path confused ruby enough to cause the same file to get interpreted twice. Signed-off-by: Jesse Wolfe <jes5199@gmail.com>
* | Fix #3150 - require function doesn't like ::class syntaxBrice Figureau2010-02-172-0/+18
| | | | | | | | Signed-off-by: Brice Figureau <brice-puppet@daysofwonder.com>
* | Added time module to tagmail reportJames Turnbull2010-02-171-0/+1
| |
* | Fixed the return types were valid, and removed the copy paste error with the ↵Bryan Kearney2010-02-172-7/+7
| | | | | | | | exception logic
* | Resolving conflicts with ???Markus Roberts2010-02-171-1/+1
| | | | | | | | This actually fixes a bug in the patch, not a conflict per se, but it was small and this was the easiest way to fix it.
* | Add AIX package management support (installp&nim)Andrew Forgue2010-02-174-0/+281
| | | | | | | | | | | | | | | | | | | | This patch adds support for the native AIX package manager. It allows installation from either the name of an lpp_source (if you have a NIM environment configured, or from a directory containing .bff files. Signed-off-by: Andrew Forgue <andrew.forgue@gmail.com>
* | Fixing #3148 Settings#without_noop when run with no noop settingLuke Kanies2010-02-172-3/+9
| | | | | | | | | | | | | | Some tests didn't define this setting which caused this method to fail. Signed-off-by: Luke Kanies <luke@reductivelabs.com>
* | Move scope parenting & class_scope from Compiler to ScopeMarkus Roberts2010-02-176-101/+97
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This refactor fixes about a quarter of the test failures on master and (I hope) will simplify some of the integration issues on the testing branch. It is my best guess at The Right Thing To Do (or at least a step in that direction) but I could be persuaded otherwise. The basic idea is to take responsibility for maintaining scope hierarchy and class_name -> class_scope mapping out of the compiler class and put it in the scope class where it arguably belongs. To maintain the semantics, class scopes are all tracked by the "top level" scope, though this could be relaxed if the nesting semantics were ever needed. If this winds up being the right thing to do, related routines (e.g. newscope) should be sorted out as well.
* | [#3392] Better Rakefile, remove puppetmasterd specRein Henrichs2010-02-172-163/+6
| | | | | | | | | | - Minor improvements to Rakefile spec task - Remove puppetmasterd spec, to be run as part of the testing matrix
* | Fixing tests in pkg providerMarkus Roberts2010-02-171-6/+6
| |
* | bug #3407 Part 2Jesse Wolfe2010-03-221-1/+1
| | | | | | | | | | | | | | My change to the Puppet::Module::InvalidName error's initializer broke a spec in a different file. Signed-off-by: Jesse Wolfe <jes5199@gmail.com>
* | Fixing #3407 Failing tests in spec/unit/node/environment.rbJesse Wolfe2010-03-223-19/+21
| | | | | | | | | | | | | | | | | | A naked rescue in Puppet::Node::Environment was hiding expectation violations from the Mocha mocks. Specifically, 'modulepath' expectations were failing, as Puppet::Module now calls Puppet::Node::Environment#modulepath internally. Signed-off-by: Jesse Wolfe <jes5199@gmail.com>
* | Bug #3406 augeas spec fails if there is not a default providerJesse Wolfe2010-03-221-0/+2
| | | | | | | | | | | | So I stubbed out the default provider. Signed-off-by: Jesse Wolfe <jes5199@gmail.com>
* | Bug #3402 Stub returning invalid type for :noopJesse Wolfe2010-03-221-1/+2
| | | | | | | | | | A stub was causing a test failure by returning a string for a parameter that requires a boolean.
* | Bug #3401 Spec failed due to missing manditory setting in mockJesse Wolfe2010-03-221-2/+6
| | | | | | | | | | Puppet::Util::Settings#use now requires the :noop setting to exist, and this test was not providing one in its mocked default structure.
* | Bug #3400 Bad mocks causing failing testsJesse Wolfe2010-03-221-1/+3
| | | | | | | | | | | | New code was calling a mocked method that was stubbed too broadly, causing the whole thing to act strangely. I've tightened the existing stub and stubbed the new method call.
* | Fix #3167 Duplicate constant warnings in dpkg.rbJesse Wolfe2010-02-172-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | There's a limitation in Ruby 1.8.x that makes constants behave differently than developers seem to expect: Constants defined inside a do/end block do not get inserted into the namespace of 'self', they instead go into the toplevel (Object) namespace. These providers exhibit bugs since they use constants with the same name in the same namespace. Other providers and other dynamically generated classes using constants without an explicit namespace should be considered to have a code smell. Signed-off-by: Jesse Wolfe <jes5199@gmail.com>
* | Merge branch '0.25.x'Markus Roberts2010-02-0958-1440/+1056
|\| | | | | | | | | | | | | | | | | | | Conflicts: lib/puppet/agent.rb lib/puppet/application/puppet.rb lib/puppet/configurer.rb man/man5/puppet.conf.5 spec/integration/defaults.rb spec/unit/configurer.rb
| * Fixed #3162 - tidy does not remove empty files when "size => 0" is setJames Turnbull2010-02-092-1/+7
| | | | | | | | | | | | Thanks to Stig Sandbeck Mathisen for the fix See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513309
| * Fixed #3128 - Updated man pages and moved puppet.conf.8 to puppet.conf.5James Turnbull2010-02-097-1090/+723
| |
| * Add version number to puppetlast display.Mark Plaksin2010-02-081-1/+1
| | | | | | | | | | | | Move "cache expired" to the end of puppetlast lines. This way the number of seconds and puppet version are always in the same column.
| * Forgot fakedata called in specJames Turnbull2010-02-041-0/+1
| |
generated by cgit (git 2.34.1) at 2025-09-28 19:46:23 +0000