summaryrefslogtreecommitdiffstats
path: root/lib/puppet
Commit message (Collapse)AuthorAgeFilesLines
...
| * | [#4716] ResourceTypeAPI exposes implementation details that are likely to changePaul Berry2010-09-223-15/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Made the following modifications to ResourceTypeAPI: (1) returned nil from “define”, “hostclass”, and “node”. (2) renamed “mk_resource_type” and “munge_type_arguments” to “__mk_resource_type__” and “__munge_type_arguments__” to discourage customers from calling them. (3) Made ResourceTypeAPI a class rather than a module, and changed the parser to evaluate the contents of pure ruby manifests using a instances of this class. (4) Changed ResourceTypeAPI to insert newly instantiated types into Thread.current[:known_resource_types] rather than the default environment's known_resource_types. This effectively backports the fix for issue #4657 to 2.6.x. Also backported the new spec tests from #4657.
* | | Partial merge to 2.6.2rc1 : Merge commit '8ff4b9a' into nextJesse Wolfe2010-10-021-1/+1
|\| | | | | | | | | | | There are merge conflicts with commits following this one.
| * | Fixed #4819 - corrected cron documentationJames Turnbull2010-09-231-1/+1
| | |
* | | Partial merge to 2.6.2rc1 : Merge commit '2b50f30' into nextJesse Wolfe2010-10-022-59/+59
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Commit 2b50f30 simplified and fixed bugs in code that had already been modified extensively by 4da88fb and 6b1dd81. This merge resolution commit is a manual replay of the changes from 2b50f30 onto next. Manually Resolved Conflicts: lib/puppet/parser/type_loader.rb spec/unit/parser/type_loader_spec.rb
| * | [#4771] Import of manifests with the same name only happens oncePaul Berry2010-09-232-49/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The function import_if_possible, which was supposed to be responsible for making sure that no two threads tried to import the same file at the same time, was not making this decision based on the full pathname of the file, since it was being invoked before pathnames were resolved. As a result, if we attempted to import two distinct files with the same name at the same time (either in two threads or in a single thread due to recursion), one of the files would not always get imported. Fixed this problem by moving the thread-safety logic to happen after filenames are resolved to absolute paths. This made it possible to simplify the thread-safety logic significantly.
* | | Partial merge to 2.6.2rc1 : Merge commit '7b8cb74' into nextJesse Wolfe2010-10-029-38/+41
|\| | | | | | | | | | | There are merge conflicts with commits following this one.
| * | Fix for #4708 - tagmail should allow . in tagnameDan Bode2010-09-231-1/+1
| | | | | | | | | | | | changed the regex so that tagmail allows . in tagname.
| * | Minimal fix for #4631 -- set implicit classes as in 0.25.xMarkus Roberts2010-09-231-0/+7
| | | | | | | | | | | | | | | | | | | | | This is a minimal fix for #4631 by reversing one part of the refactor for #1903 commit 0d4fd60c7c143cc1f4e4b0f99f359c09cbfbf21e. It fixes the immediate issue (implicit classes not being added to resources) but leaves open several other questions which are defered to #4687.
| * | Fixed #3707 - rpm, like dpkg-query exits 1 if the package is not installed. ↵James Turnbull2010-09-231-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Returning nil in this provider had the effect that on every run, puppet would end up calling yum erase . Returning the correct data structure resolves this. Thanks to Stephen Gran for the patch
| * | Fixed Puppet Doc TOC generationJames Turnbull2010-09-161-2/+2
| | |
| * | Fixed versioncmp function typoJames Turnbull2010-09-161-1/+1
| | |
| * | Documentation updates for Markdown conversionJames Turnbull2010-09-146-34/+29
| | |
* | | Merge commit '2.6.1' into nextJesse Wolfe2010-09-133-10/+23
|\| |
| * | [#4756] addendum for #4756Jesse Wolfe2010-09-141-7/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes spec and unit tests indirectly related to the previous patch-revert. One failure was from trying to test the User Type's roles, when, on many platforms, the roles feature wasn't supported by the default Provider. Other tests could fail on some platforms because they assumed that unsupported attributes would be ignored with a warning, but the code was crashing instead.
| * | Fix for Bug #4756 - Providers no longer respect missing featuresJames Cammarata2010-09-141-0/+6
| | | | | | | | | | | | Restored deleted lines from type.rb and reinstated unit tests
| * | Fix for #4736 -- preserve case of defined resourcesMarkus Roberts2010-09-101-2/+7
| | | | | | | | | | | | | | | | | | This restricts the change introduced in #4691 to hostclasses, and leaves defined resources and nodes alone, thus more closely mimicing the 0.25.x behaviour. It also includes title, as this was similarly affected.
| * | Fix for #4637 --use of namevar missed in refactorMarkus Roberts2010-09-091-1/+1
| | | | | | | | | | | | | | | A use of namevar apparently slipped through the net or got (re)introduced in a merge/conflict resolution.
* | | Merge commit '2.6.1rc4' into nextJesse Wolfe2010-09-1314-153/+178
|\| |
| * | Minimal fix for #4691 -- class name uppercased in $nameMarkus Roberts2010-09-071-1/+1
| | | | | | | | | | | | | | | | | | The class name is now stored internally with an initial capital, which changed the contents of $name in a way that broke some manifests. This fix stores the downcased version in $name.
| * | Fix for #4693 -- implicit stages should never be serializedMarkus Roberts2010-09-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | My fix for #4542 was overly enthusiastic about assuring that all resources had a stage, resulting in stages designations being serialized for resources in manifests which did not use resources (everything was in implicit main). This broke 0.25.x compatibility, as all catalogs now refered to stages. This patch scales back the change for #4542 slightly, supressing the setting of main on the puppetmaster and relying on the default behaviour on the client (for 2.6.x and later, treat it as main; for 0.25.x, do nothing).
| * | Fix for tests broken by fix for #4489 -- stub standaloneMarkus Roberts2010-09-071-1/+5
| | | | | | | | | | | | | | | | | | If the file streaming is to be thwarted when running standalone the test for standalone needs to be stubbed when running specs, lest the tests inexplicably fail.
| * | Fix for #4489 -- apply was using the rest terminusMarkus Roberts2010-09-072-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Basing pervasive low-level behaviour changes on the application name isn't a good idea, but if we're going to do it we need to remember to update the test when we rename the application. Further, if we optimize around such low-level tests (as we did when implementing file-streaming) we need to carry the tests over into the new data paths. This commit addresses both of these isues, restoring 0.25.x stand-alone file serving by adjusting the process-name test in the indirector to recognize "apply" as standalone (and thus not use http to fetch the files) and by adding a branch to the file streaming code to do the same when fetching the content. I am not certain that this change is globally correct; there may be other related problems that will not be fixed (and may in fact be exacerbated) by this patch.
| * | [#4462] uncaught Timeout::ErrorJesse Wolfe2010-09-071-1/+3
| | | | | | | | | | | | | | | | | | puppet agent was not catching all species of exceptions, causing it to crash on net/http timeout errors. This patch broadens the types of exceptions that are caught.
| * | Fixed alias metaparam docs errorJames Turnbull2010-09-071-1/+1
| | |
| * | Skip apt-listbugs and apt-listchanges when installing from puppetDean Wilson2010-09-041-0/+4
| | |
| * | Fixed queue require for #4555James Turnbull2010-09-031-1/+1
| | |
| * | Fixed #4100 - Added http_caching to yumrepo typeJames Turnbull2010-08-311-0/+6
| | |
| * | Added cost parameter to the yumrepo typeJames Turnbull2010-08-311-0/+6
| | |
| * | Fixed extlookup documentation and spacingJames Turnbull2010-08-312-143/+134
| | |
| * | Fix for #4506 -- too much data being serializedMarkus Roberts2010-08-311-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The serialization of much of the memory image was being triggered by a copy of an unchanging method return value in an instance variable. I had introduced this as a performance hack. The results were correct, but when the object was serialized it took a huge amount of data with it (known_resource_types, and from there...) As the underlying costly operation is no longer being called (thanks to Paul and Jesse) the caching is no longer a significant performance boost, and can thus simply be removed.
| * | Fixed terminus example documentationJames Turnbull2010-08-292-4/+4
| | |
* | | Merge remote branch 'paul/ticket/next/4685' into nextJesse Wolfe2010-09-096-1910/+1770
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Conflicts resolved manually, by Paul Berry: lib/puppet/parser/ast/astarray.rb lib/puppet/parser/grammar.ra lib/puppet/parser/parser.rb (by rebuilding from grammar.ra)
| * | | Modified the error message that is generated when a class, definition,Paul Berry2010-09-075-141/+145
| | |/ | |/| | | | | | | | | | or node occurs in a conditional construct so that it contains the proper line number.
| * | [#4685] Classes, defines, and nodes allowed inside of non-evaluated conditionalsPaul Berry2010-09-013-1160/+1118
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, ASTArray#evaluate() was responsible for checking whether the user had tried to declare a class, define, or node in a prohibited location (such as a conditional construct). This meant that errors would only be reported to the user if the conditional code was actually evaluated. Moved the checking into the parser, so that errors are always reported.
* | | Merge remote branch 'paul/ticket/next/4638' into nextJesse Wolfe2010-09-099-463/+315
|\ \ \
| * | | [4638] Cleanup of plurals and inheritance relationships in ASTPaul Berry2010-08-279-463/+315
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changed the grammar so that the following "plural" constructs always parse as an ASTArray: - funcvalues - rvalues - resourceinstances - anyparams - params - caseopts - casevalues And the following "singluar" construct never parses as an ASTArray: - statement The previous behavior was for these constructs to parse as a scalar when they represented a single item and an ASTArray when they contained zero or multiple items. ("Statement" could sometimes represent a single item because a single resource declaration could represent multiple resources). This complicated other grammar rules and caused ambiguous handling of nested arrays. Also made these changes to the AST class hierarchy: - ResourceInstance no longer derives from ASTArray. This relationship was not meaningful because a ResourceInstance is a (title, parameters) pair, not an array, and it produced complications when we wanted to represent an array of ResourceInstance objects. - Resource no longer derives from ResourceReference. No significant functionality was being inherited and the relationship doesn't make sense in an AST context. - ResourceOverride no longer derives from Resource. No significant functionality was being inherited and the relationship doesn't make sense in an AST context. - Resource can now represent a compound resource instance such as "notify { foo: ; bar: }". This saves the parser from having to use represent a statement as an array of objects. - ASTArray's evaluate method never flattens out arrays of arrays.
* | | | Merge remote branch 'paul/ticket/next/4570' into nextJesse Wolfe2010-09-081-12/+11
|\ \ \ \ | |_|/ / |/| | |
| * | | Fixed issue #4570 (Race conditions when serializing objects to YAML).Paul Berry2010-08-231-12/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The ZAML class was using class variables to keep track of labels and backreferences while serializing object to YAML. This made it possible to get ill-formed or incorrect YAML output if two threads tried to serialize objects at the same time. Changed to use instance variables of the ZAML class, so there is no race condition. Also added some more spec tests to verify that labels are generated properly.
* | | | Merge commit '2.6.1rc3' into nextJesse Wolfe2010-08-2710-36/+42
|\ \ \ \ | |_|/ / |/| | / | | |/ | |/|
| * | Fix for #4456 -- need to accept some mime-type aliasesMarkus Roberts2010-08-242-4/+10
| | | | | | | | | | | | | | | | | | Rather than just creating a handler for the base mime-type (e.g. "text/yaml") we create some synonyms where appropriate (e.g. "text/x-yaml", "application/yaml", etc.)
| * | Fix for #4489 -- apply was using the rest terminusMarkus Roberts2010-08-241-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Basing pervasive low-level behaviour changes on the application name isn't a good idea, but if we're going to do it we need to remember to update the test when we rename the application. I am not certain that this change is globally correct; there may be other related problems that will not be fixed (and may in fact be exacerbated) by this patch.
| * | Fix for #4542 -- included classes weren't assigned proper stagesMarkus Roberts2010-08-241-13/+6
| | | | | | | | | | | | | | | | | | This commit unifies the code paths on which classes are added, alters the default stage to respect the stage of the parent if any, and assures that the resource is notified if its stage is assigned (turning an implicit stage into an explicit one).
| * | Fix for #4501 -- reports not generated in standaloneMarkus Roberts2010-08-241-5/+10
| | | | | | | | | | | | | | | | | | | | | The refactors for 2.6.x stopped "puppet apply" from saving reports; this fix adds report saving back to puppet apply but leaves a number of related issues (code path consolidation, report contents, etc.) unresolved for future patches in the 2.6.x series or more significant refactoring in 2.7.x.
| * | Start server before agentBernhard Miklautz2010-08-211-1/+1
| | |
| * | [#4555] puppet queue tries to call code it hasn't requiredJesse Wolfe2010-08-211-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | puppet queue was trying to call .subscribe on Puppet::Resource::Catalog::Queue, but that object had not been loaded into the ruby interpreter. This bug was partially masked by ruby's confusing constant resolution, which was incorrectly returning the Puppet::Application::Queue class instead of throwing a NameError
| * | fix #4528 - treat * as absentPeter Meier2010-08-211-1/+1
| | | | | | | | | | | | | | | | | | | | | Internally the cron type is seeing params containing only '*', as absent. However, if a user was setting a parameter explicitely as '*', we weren't munging it to be absent. Hence, we were setting this param over and over again.
| * | Fix for #4518 -- classes not getting added to compiler.classesMarkus Roberts2010-08-211-0/+1
| | | | | | | | | | | | | | | | | | | | | The responsibility for adding classes to the compiler's classes list (for use in constructing classes.txt) moved around a bit in the 0.25 to 2.6 transition before being dropped in a merge conflict resolution. Ooops. This restores it, and adds tests to prevent regression.
| * | Maint. -- Fix test failures broken by previous commitMarkus Roberts2010-08-211-2/+8
| | | | | | | | | | | | | | | | | | | | | This basically involved adding a search method to the yaml indirector, which I did by copying the one from ssl_file and fiddling with it until the tests passed. Since the most straight forward way to do this required extending the interface to the path method I added tests for the additional behaviour.
| * | Maint. Removing code at the request of the original authorMarkus Roberts2010-08-211-10/+1
| | | | | | | | | | | | A contributor has requested that his changes be removed from puppet.
| * | [#4298] Puppet apply prints an error if the file to apply doesn't existMatt Robinson2010-08-211-1/+4
| |/ | | | | | | | | | | | | | | Also warns you it's skipping files if you pass it more than one file to apply. Reviewed-by: Nick Lewis <nick@puppetlabs.com> Signed-off-by: Matt Robinson <matt@puppetlabs.com>
generated by cgit (git 2.34.1) at 2025-09-25 22:07:50 +0000