| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
We don't support Solaris 5.10 in Chef anymore so there's no reason to make this check every time the resource runs on Solaris 5.11
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: aklyachkin <aklyachkin@gmail.com>
|
|
|
|
| |
Signed-off-by: aklyachkin <aklyachkin@gmail.com>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Improve auto-generated docs
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
|
|
|
|
| |
Add more descriptions and examples
Remove some smart quotes
Make sure homebrew_package gets tagged as supporting multi-package
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Update to ssl_verify_mode on remote_file
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So it turns out the `berkshelf` has been passing it's entire `options`
hash into `Chef::HTTP` this whole time, which, we should probably fix.
However, one of those options was `:ssl_verify_mode`. We ignore entries
in the `options` hash we don't recognize so this was fine, but suddenly
we recognize it. But we expected it to be class, and they're passing
in symbols. Whoops!
This makes that all work and puts the symbol->class conversion inside
of `Chef::HTTP`.
Signed-off-by: Phil Dibowitz <phil@ipom.com>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Update & add resource descriptions for documentation generation
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
|
|
| |
Improve the docs we auto generate.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
CHEF_MVPS for 2019
|
| |
| |
| | |
Signed-off-by: Jason Field <jason@avon-lea.co.uk>
|
| | |
|
|/
|
|
|
| |
Adding ChefMVPs from 2019
Signed-off-by: Jason Field <jason@avon-lea.co.uk>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Add ssl_verify option for remote_file
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Different servers have different https requirements and enforcing
the API policy on all `remote_file` resources isn't reasonable.
The logic around the HTTP clients and policies in Chef is... complex.
This approach seemed like the best one, but I'm open to others.
By default here if the user specifies nothing, `remote_file`'s http
clients will fall back to the API policy, otherwise, it'll use whatever
the specify.
This fixes #8897
Signed-off-by: Phil Dibowitz <phil@ipom.com>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Add an input property to the execute resource for passing input on STDIN
|
| | |
| | |
| | |
| | | |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
| | | |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
|\ \ \
| | | |
| | | | |
Adds the homebrew_update resource
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Dan Webb <dan.webb@damacus.io>
|
| | | |
| | | |
| | | |
| | | | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \ \ \
| | | | |
| | | | | |
Add 16.1.16 release notes
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
Co-authored-by: Ian Maddaus <IanMadd@users.noreply.github.com>
|
|/ / / /
| | | |
| | | |
| | | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | | |
| | | |
| | | |
| | | | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is a breaking change to fix a breaking change in Chef 16.0.
The new behavior is that a resource which relies upon the reource_name
statement to wire the resource up to the DSL will fail (although the
very old wiring of the "<cookbook_name>_<resource filename>" continues
to work).
So for a resource which does not get its DSL wiring from the filename,
only declaring a resource_name will fail:
```
resource_name :foo
```
This can be fixed by adding an explicit `provides` line (which is
backwards compatible):
```
resource_name :foo
provides :foo
```
If backwards compatibility is not a concern, then post-16.0 the
resource_name call can be completely dropped:
```
provides :foo
```
This is a vastly simpler backwards compatibility break than the
unintentional break in #9885, which is difficult to describe and
to detect.
The rules going forward are fairly simple to explain:
1. The resource_name now only sets the resource_name.
2. The old behavior of the fallback resource_name and DSL wiring
based on the filename is preserved (unless the values are set).
3. In Chef 16, The first provides line will set the resource_name if
it has not already been set, allowing the resource_name to be
omitted.
It is recommended that all resources only set provides lines, the
use of the fallback filename-based wiring is discouraged and
explicitly setting the resource_name is discouraged.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | | |
| | | | |
| | | | |
| | | | | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \ \ \ \
| |_|_|/ /
|/| | | | |
Pull in updated omnibus-software for rubygems perf patch
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
This resolves the rubygems perf regression in the release that shipped in Ruby 2.7.x
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | | |
| | | |
| | | |
| | | | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \ \ \
| | | | |
| | | | | |
Update our usage of OpenSSL::Digest to avoid Ruby 3 breaking change
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
There's a RuboCop cop to fix these before Ruby 3 breaks it.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | | | |
| | | | |
| | | | |
| | | | | |
Obvious fix; these changes are the result of automation not creative thinking.
|