| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
this will probably help with debugging it seems like a bit of a mess
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\
| |
| | |
Chef-13: turn on zypper gpg checks by default
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Adds a gpg_check property to the resource to turn them off on a
per-resource basis. The global config is also preserved. The
global config will warn once if you have it set to turn off
gpg checks. The per-resource property will not warn (presumably
you know you're doing something bad when you turn it off).
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\ \
| | |
| | | |
Chef-13 knife search exit 1 when no results
|
| | |
| | |
| | |
| | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\ \ \
| | | |
| | | | |
Chef-13: remove deprecated knife subcommand APIs
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
otherwise things go boom immediately in rspec...
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
forgot to clean this up
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\ \ \ \
| | | | |
| | | | | |
Chef-13: coerce package options property to an Array
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Windows side we still can't support this kind of API, this
is for Unix-ey stuff.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Fix cookbook gem installer
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: Ibf4a53b9f687882f84932433cc3d45e084e3a29e
Signed-off-by: Maxime Brugidou <m.brugidou@criteo.com>
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Current gem installer does not work if multiple cookbook request the
same gem. The solution is to merge all the gem requirements for the same
gem.
If multiple cookbooks have conflicting constraints, the install will
fail anyway.
This bug affects Chef 12 too and make the feature almost unusable.
Change-Id: I73bdb3db94052dadc4bac7bf03f74db8c420aad5
Signed-off-by: Maxime Brugidou <m.brugidou@criteo.com>
|
| | | | | |
|
|\ \ \ \ \
| |_|_|/ /
|/| | | | |
Chef-13: remove iconv from the chef build
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
pulls in chef/omnibus-software#806 and removes iconv from both
nokogiri and ruby.
ruby hasn't needed iconv since 1.9.x and everyone should be using
the Encoding library by now.
nokogiri will lose support for things like Shift-JIS inside of XML
but UTF-8, UTF-16LE/BE, ISO-8851-1(Latin-1), ASCII and "HTML" encoding
are all supported by nokogiri natively. if users need more they need
to be maintaining their own nokogiri installs and accept the
maintenance costs themselves.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
Chef-13: Remove deprecated Chef::ResourceResolver.resource API
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
Removes an alias to Chef::ResourceResolver.resource_name
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
|
|\ \ \
| | | |
| | | | |
Chef-13: fix notifying array resources
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
can't wait for that 1.8 release with 2.4 support...
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
this also deprecates the multi-resource notification syntax where
`foo[a,b]` would attempt to notify both `foo[a]` and `foo[b]` because
that is hella ambiguous.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
Chef-13: remove deprecated run_command API entirely
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
i wonder what it was tesing before...
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
possibly others
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
perhaps this has been fixed now?
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|/ / /
| | |
| | |
| | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
|