summaryrefslogtreecommitdiff
path: root/chef.gemspec
Commit message (Collapse)AuthorAgeFilesLines
* Add gemspec files to allow bundler to run from the gemKartik Null Cating-Subramanian2015-10-091-1/+1
|
* Ship our Gemfile so people can run our tests from the gemjk/external-testsJohn Keiser2015-09-301-1/+1
|
* Use same mixlib-shellout version pin in chef, ohai, and chef-configJay Mundrawala2015-08-311-1/+1
|
* highline is used by core Chef; therefore remove this misleading commentJulian C. Dunn2015-08-081-1/+0
|
* Use 8.6 alpha gem of ohaiClaire McQuin2015-08-071-1/+1
|
* Mute :log_level and :log_location deprecation warnings from ohai config.Claire McQuin2015-07-271-1/+1
|
* Update rake tasks for componentizationdanielsdeleo2015-05-201-1/+1
|
* Move Chef::Config into a subprojectdanielsdeleo2015-05-201-1/+2
|
* Pull rspec helper fix from Chef Zero 4.2.2danielsdeleo2015-05-191-1/+1
|
* Add specs for many external dependent projectsJohn Keiser2015-05-131-2/+1
|
* Add tests for resource naming and creationJohn Keiser2015-05-131-0/+1
|
* add Chef::Log::Syslog classLamont Granquist2015-05-061-0/+2
| | | | | | | | | | | See: * https://www.kickflop.net/blog/2013/06/27/syslog-output-for-chef-runs/ * http://lists.opscode.com/sympa/arc/chef/2014-12/msg00152.html * https://github.com/higanworks-cookbooks/chef-client_syslog It is relatively embarrassing to have a system administration tool that doesn't support syslog out of the box.
* use validate_utf8=false option to json encoder for nodeLamont Granquist2015-05-041-1/+1
| | | | | | | with validation off any bad utf8 data will not cause the ffi-yajl encoder to raise. with ffi-yajl >= 2.2.0 the bad data will be scrubbed to produce valid JSON to POST/PUT to the server.
* Switch over Windows builds to universal builds.Kartik Null Cating-Subramanian2015-05-011-2/+2
| | | | Updated dependencies and refactored platform gemspecs.
* Update chef-zero to pull in socketless modedanielsdeleo2015-04-011-1/+1
|
* bumping ffi-yajl to pick up 2.xlcg/bump-ffi-yajlLamont Granquist2015-03-171-1/+1
| | | | 1.x still works fine, so leaving the lower floor in place.
* Bump chef-zero dep to 4.0jk/chef-zero-4.0John Keiser2015-02-111-1/+1
|
* Fixing Rspec 3.2 update. We were overriding private APIs which changed.tball/rspec32-fixtyler-ball2015-02-041-1/+1
|
* pin rspec to 3.1.x for nowLamont Granquist2015-02-031-1/+1
| | | | | rspec 3.2.0 release changed some private APIs in rspec that we were using for audit mode and broke our master (kind of expected/understandable).
* Addressing review comments, adding documentationtyler-ball2014-12-181-0/+1
|
* Adding test for recipe DSL audit additionstyler-ball2014-12-171-2/+2
|
* add rspec/itsClaire McQuin2014-12-171-8/+5
|
* Add serverspec types and matchers.Claire McQuin2014-12-171-0/+3
|
* First pass at DSL additionstyler-ball2014-12-171-1/+1
|
* pinning ohai to 8.xLamont Granquist2014-12-031-1/+1
|
* Remove all parts of 'shef'Julian C. Dunn2014-11-261-1/+1
|
* drop ruby 1.9.x support for Chef-12Lamont Granquist2014-11-251-1/+1
| | | | | | | | | | Ruby 1.9.3 is in security-only maintenance phase which means that bugs for the core ruby interpreter will not be fixed and Chef cannot support ruby 1.9.x. Users should be using omnibus-chef packages which come with a built-in ruby 2.x or should upgrade their own installations to ruby 2.x (and accept that ongoing upgrade and support cost). Chef 11 will continue to be shipped on ruby 1.9.x until Chef 11 is EOL.
* Merge branch 'master' into mcquin/rspec-3Claire McQuin2014-11-071-4/+1
|\
| * Only include chef-service-manager on windowsjdmundrawala/gemspecJay Mundrawala2014-10-211-4/+1
| |
* | Bump to rspec 3.Claire McQuin2014-10-291-2/+2
|/
* Adding a bin for windows service so that we can appbundleJay Mundrawala2014-10-211-1/+1
|
* Upgrading to latest ffi-yajl which contains fixes for Object#to_jsontyler-ball2014-10-101-1/+1
|
* Updating to latest chef-zero since that dropped json dependencies tootyler-ball2014-10-071-1/+1
|
* Trying to eradicate all traces of the JSON gem from Cheftyler-ball2014-10-071-1/+1
|
* pull ohai rc releaseLamont Granquist2014-09-091-1/+1
| | | | | if we don't specifically pull the rc release then we can't depsolve mixlib-shellout 2.x
* bump mixlib-shellout to 2.0, track ohai+mixlib-shellout masterLamont Granquist2014-09-081-2/+1
|
* unicode shell_out fixes plus mixlib-shellout 2.xLamont Granquist2014-09-081-0/+1
| | | | | | - use en_US.UTF-8 explicitly rather than relying on mixlib-shellout's 'C' locale in order to force the LANG by default (restores unicode to most chef-client calls now)
* Update license to appropriate SPDX IDBryan McLellan2014-09-031-1/+1
|
* Add license information to gemspecAnatol2014-09-031-0/+1
| | | | Obvious fix.
* Switch back to ChefZero::RSpec version 3jk/rspec_zero_3John Keiser2014-08-291-1/+1
| | | | And add some Enterprise tests (fix an acl delete issue)
* Widen chef-zero dependency correctlyJohn Keiser2014-08-281-1/+1
|
* Update to chef-zero 3John Keiser2014-08-221-1/+1
|
* * Dscl user provider changes to support Mac 10.7, 10.8 & 10.9.Serdar Sutay2014-08-121-1/+2
| | | | | | * Make the dscl user provider password handling idempotent. * Refactor / modernize dscl user provider unit tests. * Functional tests for dscl user provider.
* Fix error class typo, bump ffi-yajl requirement to pull in bugfixesdanielsdeleo2014-08-121-1/+1
|
* deprecated ruby 1.8.7 through 1.9.2Lamont Granquist2014-07-261-0/+2
|
* set ohai version constraint for releaseLamont Granquist2014-07-231-1/+1
| | | | | Conflicts: chef.gemspec
* remove rest-client gemLamont Granquist2014-07-171-10/+0
| | | | nothing in chef-client uses it any more.
* Merge pull request #1636 from opscode/lcg/ffi-yajl-constraintlamont-granquist2014-07-171-1/+1
|\ | | | | pin ffi_yajl to 1.0.0 with semver constraint
| * setting proper semver constraint on ffi-yajlLamont Granquist2014-07-161-1/+1
| | | | | | | | ffi-yajl 1.0.0 has been relesed
* | Update gemspec URL and domain nameJulian C. Dunn2014-07-161-2/+2
| |