| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Tom Duffield <tom@chef.io>
|
|
|
|
| |
Signed-off-by: Salim Afiune <afiune@chef.io>
|
|
|
|
| |
Signed-off-by: Salim Afiune <afiune@chef.io>
|
|
|
|
| |
Signed-off-by: Salim Afiune <afiune@chef.io>
|
|
|
|
| |
Signed-off-by: Salim Afiune <afiune@chef.io>
|
| |
|
|\
| |
| | |
Chef-13: freeze merged node attribute
|
|/
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
|
|\
| |
| | |
[ci skip] add missing relnotes for Node deep-duping
|
|/
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
|
|\
| |
| | |
Chef-13: properly deep dup Node#to_hash
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
similarly to fixing to_hash.
kind of feels like we should return a VividMash instead of a Mash
here, to get a writable thing that behaves like an attribute...
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
previously to_hash allowed mutating non-container elements, now
they get properly dup'd.
fixes a 2.5 year old pending spec test.
also fills out the API so that there is to_h/to_hash/to_a/to_array
instead of the weird mix-and-match we had before.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | |
|
|\ \
| | |
| | | |
Add release policy badge to README
|
|/ /
| |
| |
| | |
Signed-off-by: Tom Duffield <tom@chef.io>
|
| | |
|
|\ \
| | |
| | | |
bump ruby to 2.3.3
|
| | |
| | |
| | |
| | |
| | |
| | | |
i think we need to change this here as well.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
can finally do this now that the branching nightmare is gone.
not bumping to 2.4.0 because of:
- perf regression in rspec and waiting for 2.4.1
- not wanting to buy that yak shave yet
- iterative development and moving the needle forwards in
small increments
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
|
|\ \ \
| |/ /
|/| | |
No more easy_install resource.
|
| | |
| | |
| | |
| | | |
Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Chef-13: Remove declare_resource create_if_missing API
|
| | |
| | |
| | |
| | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Likely nobody cares about this change, I added it and then a
release or two later introduced the better edit_resource style
of API.
I also changed "created_at" to be a proper named parameter, instead
of a positional parameter, which is a breaking change in an API that
has been around for quite some time -- makes the API consistent since
I added it as a named parameter to the new APIs when I wrote them.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Kill JSON auto inflate with fire
|
| | |
| | |
| | |
| | | |
Signed-off-by: Thom May <thom@chef.io>
|
| | | |
|
|\ \ \
| |_|/
|/| | |
OSX maintainer
|
| | |
| | |
| | |
| | | |
Signed-off-by: Mike Dodge <mikedodge04@gmail.com>
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Mike Dodge <mikedodge04@fb.com>
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add myself to OSX Maintainers
Signed-off-by: Mike Dodge <mikedodge04@fb.com>
|
| | |\ \ |
|
| |/ / /
| | | |
| | | |
| | | | |
Signed-off-by: Mike Dodge <mikedodge04@fb.com>
|
| |\ \ \ |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Chef-13: remove method_missing access to node object.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
So again the reasons why we break this:
- node.class vs. node['class'] kinds of problems
- adding node#foo to Chef::Node as an extension to the API and
breaking node.foo meaning node["foo"] (we can't make exensions
to that class without possibly breaking someone)
- crazy things like the old CHEF-3799 issue in the old ticketing
system where IO#puts in ruby blindly calls #to_ary on stuff and
expects it to raise -- whereas we would potentially autovivify
a 'to_ary' hash key and return nil which breaks the world.
This also has caused issues with the hashie gem and they've gone to
spamming warnings by default to try to deal with it:
https://github.com/berkshelf/berkshelf/issues/1665
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | | | |
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
simplify dependency bumping rake tasks and bump all deps
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
this eliminates all the "run gem pristine" warning spam
and i believe uses "bundle lock" correctly.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|