summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Try to apply dsc configuration even if what-if failsjdmundrawala/issue-2169Jay Mundrawala2014-10-082-7/+7
|
* Merge pull request #2103 from opscode/jdmundrawala/issue-2027-masterJay Mundrawala2014-10-084-153/+167
|\ | | | | We now check for powershell/dsc compat in provider.
| * We now check for powershell/dsc compat in provider.jdmundrawala/issue-2027-masterJay Mundrawala2014-09-224-153/+167
| | | | | | | | | | | | | | | | The problem with raising an exception when the resource is created was that it was not possible to have a chef recipe that installs the correct version of powershell and then runs the dsc_script resource. See https://github.com/opscode/chef/issues/2027
* | Merge pull request #2102 from opscode/tball/homebrew-ownerTyler Ball2014-10-0710-132/+307
|\ \ | | | | | | `brew` command now ran as user owning executable
| * | Fixing testtyler-ball2014-10-071-16/+19
| | |
| * | Moving documentation to a more logical place. Also no longer dis-allowing ↵tyler-ball2014-10-073-15/+18
| | | | | | | | | | | | users from running brew as root.
| * | Fixing documentation errorstyler-ball2014-10-072-5/+60
| | |
| * | Missed file on last committyler-ball2014-10-071-3/+2
| | |
| * | Providing documentation for end-users, updating code with PR commenttyler-ball2014-10-071-0/+35
| | |
| * | homebrew_owner now tries to run homebrew as the user who owns the `brew` ↵tyler-ball2014-10-079-132/+212
|/ / | | | | | | executable, or an optional homebrew_package resource attribute
* | Merge pull request #2178 from opscode/lcg/serverspec-2Lamont Granquist2014-10-072-64/+21
|\ \ | | | | | | serverspec 2 fixes
| * | serverspec 2 fixes to e2e testsLamont Granquist2014-10-072-64/+21
| | | | | | | | | | | | also some cleanup in the os-detection
* | | Add a line for the fix to issue 1563 (broken git shallow-clone).Chris Doherty2014-10-071-0/+1
|/ /
* | Remove space before paren (ruby warning)danielsdeleo2014-10-061-1/+1
| |
* | Merge pull request #2154 from opscode/btm/group_functional_testsBryan McLellan2014-10-041-4/+7
|\ \ | | | | | | Match group func tests to specification
| * | Cleanup commented out codebtm/group_functional_testsBryan McLellan2014-09-291-2/+0
| | |
| * | Match group func tests to specificationBryan McLellan2014-09-291-4/+9
| | | | | | | | | | | | | | | | | | | | | When a group does not exist, the group resource should raise an exception on action modify, but not on action_manage. Also update the `not_to raise_error(SpecificError)` deprecated syntax.
* | | Merge pull request #2148 from mal/issue/1563Chris Doherty2014-10-032-0/+20
|\ \ \ | | | | | | | | Work around breaking change in git clone
| * | | Work around breaking change in gitMal Graty2014-10-022-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In git 1.7.10 shallow clone behavior was changed from shallow cloning all branches by default, to only shallow cloning the branch being checked out. Unfortunately, this breaks prior and expected behavior in Chef as, on subsequent deploys it is not possible to switch branch, because no other branches exist in the cache-copy of the repo. To fix this we must use the `--no-single-branch` flag when performing the inital clone. Unfortunately this flag is not supported by git versions prior to 1.7.10, so we must check the version of git before deciding if the workaround is required. It probably makes sense to make this prior behavior optional in a future patch, however this one just seeks to give consistent results across all versions of git.
* | | | Merge pull request #2156 from opscode/lcg/50x-errors-changeloglamont-granquist2014-10-021-0/+2
|\ \ \ \ | |_|/ / |/| | | add changelog for 50x errors
| * | | add changelog for 50x errorslcg/50x-errors-changelogLamont Granquist2014-10-021-0/+2
|/ / /
* | | Merge pull request #1912 from jessehu/CHEF-ISSUE-1904Claire McQuin2014-10-022-13/+23
|\ \ \ | | | | | | | | retry on HTTP 50X Error when calling Chef REST API
| * | | read http_retry_count from chef config in the spec; add HTTP error code in ↵Hui Hu2014-09-042-3/+4
| | | | | | | | | | | | | | | | the log.
| * | | retry on HTTP 50X Error when calling Chef REST APIHui Hu2014-08-252-13/+22
| | | |
* | | | Merge pull request #2141 from opscode/mcquin/Issue-2090Claire McQuin2014-10-021-5/+5
|\ \ \ \ | |_|/ / |/| | | Deprecate CookbookVersion#latest_cookbooks
| * | | Alias #latest_cookbooks.mcquin/Issue-2090Claire McQuin2014-09-302-10/+5
| | | |
| * | | Deprecate CookbookVersion#latest_cookbooksClaire McQuin2014-09-302-1/+6
| | | |
* | | | Merge pull request #2101 from opscode/mcquin/Issue-1910Claire McQuin2014-10-0110-136/+319
|\ \ \ \ | | | | | | | | | | Disable unforked interval runs.
| * | | | Test signal safely on windowsmcquin/Issue-1910Claire McQuin2014-10-012-1/+2
| | | | |
| * | | | Fix wording, add updates for interval sleep first, signal processingClaire McQuin2014-10-012-13/+23
| | | | |
| * | | | Tidy up some comments, whitespace.Claire McQuin2014-10-013-4/+5
| | | | |
| * | | | Update for removed unforked interval client runs.Claire McQuin2014-10-013-0/+18
| | | | |
| * | | | Reconfigure signal trapping.Claire McQuin2014-10-013-60/+133
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Exit gracefully when sent TERM Fix spec.
| * | | | Do interval and splay sleep before running client.Claire McQuin2014-10-012-25/+26
| | | | |
| * | | | Disable unforked interval runs.Claire McQuin2014-10-017-82/+161
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Clarify error message. Move fork and interval logic to application (specs pending). Clean code logic, fix specs. Allow unforked client runs with daemonize or splay
* | | | Update CHANGELOG for guard updatesBryan McLellan2014-10-011-0/+2
| | | |
* | | | Update guard functional tests for refactoringbtm/guard-orderBryan McLellan2014-10-011-1/+2
| | | | | | | | | | | | | | | | | | | | We now raise a little late when given a guard interpreter and a block, mostly being lazy. This updates the functional test to check the correct code path.
* | | | Re-remove tests that were removed in 6591d4b2Bryan McLellan2014-10-011-20/+0
| | | | | | | | | | | | | | | | | | | | These tests are no longer correct since we don't allow passing a block with a guard interpreter.
* | | | Unsupported block exception is now raised by configureBryan McLellan2014-09-301-5/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The fix for #1943 moved some code into a new configure method, which is also where we now raise if we're passed a block and a guard_interpreter as that is where we evaluate guard interpreters. This updates the unit test for that behavior.
* | | | Remove duplicate exceptionBryan McLellan2014-09-301-1/+3
| | | | | | | | | | | | | | | | | | | | We already check for command || block_given? in initialize, so command cannot be nil && not have a block when we get here.
* | | | Refactor resource guard interpreter specsBryan McLellan2014-09-301-15/+16
| | | | | | | | | | | | | | | | | | | | Refactor the unit tests to not test Chef::GuardInterpreter::ResourceGuardInterpreter directly rather than through Chef::Resource.
* | | | unit test for guard_interpreter creation during compilationBryan McLellan2014-09-302-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | make sure we don't evaluate the guard_interpreter immediately, i.e. during compilation of the resource, as the conditional may be seen before the guard_interpreter attribute.
* | | | refactor conditional to evaluate for guards laterBryan McLellan2014-09-301-7/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If we don't create the guard_interpreter until we're ready to test it, we're sure to already have all the resource attributes evaluated. Previously we set up the guard_interpreter upon initialization, that is when it was first set on the resource.
* | | | test guard_interpreter orderBryan McLellan2014-09-301-0/+13
| | | | | | | | | | | | | | | | | | | | adds a functional test to ensure guard_interpreter can be set after a conditional.
* | | | nest powershell guard functional testsBryan McLellan2014-09-301-155/+176
| | | | | | | | | | | | | | | | | | | | | | | | reorder the powershell functional tests to provide a framework for testing with guard_interpreter set and not set (allowing testing the "default", i.e. values on resource initialization).
* | | | Improve tests for no conditional casesBryan McLellan2014-09-301-2/+4
| | | | | | | | | | | | | | | | | | | | The tests that ensured we didn't run a conditional when it wasn't specified had no expectations, so they would always have passed.
* | | | update functional tests for guard_interpreterBryan McLellan2014-09-302-21/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | we now raise an error when passed a block and a guard_interpreter is specified other than :default. When other interpreters become the "default" (which actually means use the default shell for that platform) we will need to consider those as well, i.e. #1495.
* | | | guard_interpreter requires a commandBryan McLellan2014-09-302-0/+14
|/ / / | | | | | | | | | | | | | | | | | | | | | Raises an exception if guard_interpreter is set (not :default) and we are not given a command (i.e. we are given a block). This is not supported, as we pass a command to an external interpreter. Related to #1943
* | | Merge pull request #2136 from opscode/jdmundrawala/provider-specsJay Mundrawala2014-09-304-0/+6
|\ \ \ | | | | | | | | Jdmundrawala/provider specs
| * | | dos2unix revision_specjdmundrawala/provider-specsJay Mundrawala2014-09-301-111/+111
| | | |
View Lorry Controller Status