summaryrefslogtreecommitdiff
path: root/spec/data
Commit message (Collapse)AuthorAgeFilesLines
* Reduce size of nested JSON test to 252 deepbtm/lower-json-nest-testsBryan McLellan2015-04-201-2/+2
| | | | | | I got confused running git on the tester with my last commit for #3101. This should clean it up.
* Merge pull request #3102 from chef/btm/lower-json-nest-testsThom May2015-04-162-4/+2
|\ | | | | Reduce size of json nested entries
| * Reduce size of json nested entriesBryan McLellan2015-04-152-4/+2
| | | | | | | | | | | | | | | | On FreeBSD 10.1 i386 we're seeing rspec 3.2.2 raise SystemStackError if the expect line has a nested hash of 255 levels. I'm going to guess we don't even need this many. I lowered this test from 1000 to 300 arbitrarily some time ago. Fixes #3101
* | add resource_resolver and resource_priority_mapLamont Granquist2015-04-152-2/+3
|/ | | | also wire them up through the Chef class.
* fix masterLamont Granquist2015-01-251-0/+0
| | | | | | | | | | | | broken by merging #2431. code was actually broken and the specs were broken, not sure how it got into ready-to-merge in that state. rolled back the FileUtils.rm_rf that was in the original patch since it trashed my chef git repo and in light of: https://github.com/ValveSoftware/steam-for-linux/issues/3671 i think the rm_rf is a bad idea.
* try to add testsVasiliy Tolstov2015-01-251-0/+0
| | | | Signed-off-by: Vasiliy Tolstov <v.tolstov@selfip.ru>
* Added provides to provider in specJay Mundrawala2014-12-081-0/+1
|
* Added comment about change in bar.rbjdm/lwrp-providesJay Mundrawala2014-12-051-1/+1
|
* Added a provides to lwrp in spec to cover that caseJay Mundrawala2014-12-051-0/+1
| | | | Note -- This test fails
* Merge pull request #2149 from JeanMertz/chef_client_no_check_files_subdirSerdar Sutay2014-10-102-0/+4
|\ | | | | knife upload fails due to "wrong" ruby syntax in files/* file
| * Skip checking files/**/*.rb files when doing syntax checksJean Mertz2014-10-082-0/+4
| | | | | | | | | | Chef should not be concerned with Ruby syntax in files delivered through the `cookbook_file` provider.
* | Merge pull request #2165 from coderanger/rfc017Serdar Sutay2014-10-102-0/+0
|\ \ | | | | | | RFC 17 implementation
| * | Tests for new loader behavior.Noah Kantrowitz2014-10-042-0/+0
| |/ | | | | | | | | Conflicts: spec/unit/cookbook_version_spec.rb
* | Merge pull request #2129 from JeanMertz/library_subfoldersSerdar Sutay2014-10-102-0/+7
|\ \ | | | | | | [CHEF-672] load library folder recursively
| * | load library folder recursivelyJean Mertz2014-10-022-0/+7
| |/
* | Merge pull request #2193 from opscode/sersut/no-lwrp-class-reloadSerdar Sutay2014-10-094-17/+21
|\ \ | | | | | | Don't override LWRP resources or providers anymore in Chef 12.
| * | Don't override LWRP resources or providers anymore in Chef 12.Serdar Sutay2014-10-084-17/+21
| |/
* | Fixing some more changes I missedtyler-ball2014-10-072-2/+2
|/
* fix typo in commentLamont Granquist2014-08-136-6/+6
|
* adding some comments to fixturesLamont Granquist2014-08-136-0/+12
|
* * Dscl user provider changes to support Mac 10.7, 10.8 & 10.9.Serdar Sutay2014-08-128-0/+2301
| | | | | | * Make the dscl user provider password handling idempotent. * Refactor / modernize dscl user provider unit tests. * Functional tests for dscl user provider.
* Make `name` a required attribute in metadatadanielsdeleo2014-08-129-0/+37
|
* Ignore non-critical errors when finding the cookbook setdanielsdeleo2014-08-123-0/+22
| | | | | | | | | | | | https://tickets.opscode.com/browse/CHEF-2923 When running `knife cookbook upload SPECIFIC_COOKBOOK`, errors in metadata files for unrelated cookbooks should not be raised; however, we must evaluate the metadata for all cookbooks in order to allow the metadata `name` attribute to be different from the cookbook directory's basename. Therefore, we must tolerate errors in metadata.rb and re-raise them only when attempting to load the cookbook with the invalid metadata.
* Respect metadata name attributedanielsdeleo2014-08-123-0/+20
| | | | Fixes CHEF-3307
* Ammended test data to allow unit tests to verify only erb files in the ↵Victor Hahn2014-07-281-0/+2
| | | | templates directory are considered in syntax checks
* Update the expired cert for specs.sersut2014-06-161-35/+57
|
* Wrap code in an instance_eval context for syntax check.danielsdeleo2014-04-092-0/+3
| | | | | | This evaluates the code in a context similar to what Chef does when compiling recipes, so that idioms like using `return` to end evaluation of a recipe will work.
* CHEF-4203: Honor the chefignore file for knife cookbook testMatt Veitas2014-03-284-0/+14
| | | | In the case that a standalone cookbook exists that is using bundler, a large amount of gems can be added to the current directory. This commit reads the chefignore file and avoid having to scan through the ruby files that are in the bundler created gems directory.
* CHEF-4849: Implement `#response_file_variables` in Package resourcePeter Fern2013-12-201-0/+1
| | | | | | | | Now that Chef properly supports a package `response_file` using `Chef::Resource::Template`, the Package resource should implement the `response_file_variables` method so that variables do not have to exist as node attributes (eg - for seeding DB passwords for configuration files generated by packages).
* Add a directory where trusted certs can be storeddanielsdeleo2013-10-174-0/+109
|
* [CHEF-3609] Test no_proxy entries during bootstrapSean Horn2013-10-101-0/+2
|
* Prevent duplicate keys in cookbook version JSONSeth Falcon2013-10-101-0/+8
| | | | | | | | | | | | | | | | Reported in CHEF-4571. The recipes component of cookbook version metadata (cbv.metadata.recipes) serialized to JSON with duplicate keys if a metadata.rb was present that provided a recipe line matching the cookbook name (providing a description for the default recipe). The root cause is the behavior of the JSON serialized when called on a hash containing matching string and symbol keys. For example: chef > {"key1" => "sam", :key1 => "wat"}.to_json => "{\"key1\":\"sam\",\"key1\":\"wat\"}" So the specific fix is to prevent inserting a symbol key for the recipe name.
* revert whitespace for all spec/data fixturesLamont Granquist2013-09-2642-53/+53
| | | | | | - some of these have deliberate whitespace/line-ending differences - without going through them one by one its safer to revert the lot of them
* undo whitespace changeLamont Granquist2013-09-261-1/+1
|
* Reset some_windows_line_endings test fixtureSeth Vargo2013-09-261-1/+2
|
* Normalize whitespace on all filesSeth Vargo2013-09-2644-56/+55
|
* Verify that templates are preferred to files for preseedingdanielsdeleo2013-08-021-0/+4
|
* Fix bad const. ref in deprecation/provider/templatedanielsdeleo2013-08-021-1/+1
| | | | | | | | | | | | | | Fixes CHEF-4406 http://tickets.opscode.com/browse/CHEF-4406 Calls to Chef::Provider::Template#template_location and #template_finder will now correctly reference the Chef::Provider::TemplateFinder class. Chef::Provider::Package#preseed_resource uses these methods expecting an error to be raised only if there is no template with the desired name, which triggers a fallback to cookbook_file-based preseed files. This patch restores the template-based preseed functionality, but will trigger deprecation warnings from within Chef::Provider::Package's internal code.
* Add functional tests for (apt) package resourcedanielsdeleo2013-08-0238-0/+246
| | | | Repro/regression test for CHEF-4406 included but is marked pending.
* Revert "Merge branch 'CHEF-3307'"Bryan McLellan2013-07-034-4/+0
| | | | | | | | This reverts commit 5713a002062c762e40e4378be6d7763eb3dd61a2, reversing changes made to 4079a344f2001c1927132e7ed6b63453f459609f. Conflicts: spec/unit/cookbook_loader_spec.rb
* CHEF-3544 Honor chefignore in cookbook syntax checkGreg Thornton2013-06-182-0/+3
|
* don't depend on line separator in partial testsdanielsdeleo2013-06-141-1/+1
| | | | | | | | | | | In some windows testing environments no line separator conversion is happening. This may be a function of git settings, or something else in our test cluster environment. In any case, line separators are irrelevant to these tests, as they are testing the partial template feature. We could remove the line endings from the test fixture files, but editors like vim add hidden newlines at the end of files, so this is difficult to maintain. Stripping the line endings within the test code is more sustainable option.
* Prevent integration tests from loading real configdanielsdeleo2013-06-101-0/+1
| | | | | | | | | | knife integration tests were picking up default config and therefore pointing at a chef-server other than the chef-zero test instance. This could potentially lead to data loss or manglement if the test code successfully runs against a production chef-server/org. To prevent the above, load a dummy config file with an added failsafe mechanism to ensure we've not loaded a real one.
* Merge branch 'master' into file-refactorsersut2013-05-315-0/+4
|\ | | | | | | | | Conflicts: lib/chef/exceptions.rb
| * [CHEF-2420] Support annotated tags in the git providerSeth Falcon2013-05-241-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Annotated tags have their own SHA and also point to a SHA in the git repo. Using git ls-remote $REPO $TAG* the tagged SHAs can be identified by the '^{}' suffix appended to the corresponding tag name. When resolving the remote reference, we now search for $TAG* and use the SHA of the tagged commit (with ^{}) if it is there and otherwise use the SHA with an exact match for $TAG (to avoid capturing anything extra via the glob used to return refs). If no revision is specified, we force 'HEAD' in the git ls-remote call to constrain what can come back from the remote. Further, we protect against a badly chosen annotated tag named 'HEAD'. The functional test suite includes a git bundle of a small example repo. We found that locally cloning this bundle provided the closest simulation of `git ls-remote` behavior. YMMV depending on git version. The test suite could be extended to improve overall coverage, but does verify the desired behavior for annotated tags.
| * Tests CHEF-3307Mal Graty2013-05-244-0/+4
| | | | | | | | | | | | | | | | | | Test cookbook loading, shadowing and metadata deprecation warnings assocaited with the CHEF-3307 changes (use of metadata name as cookbook name in preference to file system pathname). Includes new nginx cookbook (with alternate pathname) and a shadowbook with another pathname.
* | Merge pull request #795 from opscode/ss/binmode-fixesSerdar Sutay2013-05-313-0/+12
|\ \ | | | | | | Binmode and Template line endings
| * | Make sure that windows line endings are protected during template rendering.sersut2013-05-303-0/+12
| | |
* | | only test class-specific methods for compatibilitydanielsdeleo2013-05-311-1/+127
|/ / | | | | | | | | | | Generated a new method list for checking interface compatibility, removing inherited methods. This makes the test more stable across ruby versions since methods on Object may change from 1.8->1.9->2.0.
* | Pass template extensions through to partialsdanielsdeleo2013-05-291-0/+1
| | | | | | | | | | | | | | - move the new TemplateContext code into mixin/template and consolidate with ChefContext - Copy extension modules from parent template to partial template. - Functional tests for helpers with partials.
View Lorry Controller Status