| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Christopher A. Snapp <csnapp@chef.io>
|
|
|
|
| |
Signed-off-by: Christopher A. Snapp <csnapp@chef.io>
|
|
|
|
| |
Signed-off-by: Christopher A. Snapp <csnapp@chef.io>
|
|
|
|
| |
Signed-off-by: Christopher A. Snapp <csnapp@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Update chef-telemetry to 1.0.8 and InSpec to 4.19
|
|/
|
|
|
|
| |
Pin chef-telemetry since we want to avoid the dep on http
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
hostname: Improve the windows reboot message
|
| |
| |
| |
| |
| |
| | |
Make sure this works in cinc
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|/
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
hostname: Remove support for Solaris 5.10
|
| |
| |
| |
| | |
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>
|
|\ \
| | |
| | | |
Make sure file is properly scoped in cron_access
|
|/ /
| |
| |
| |
| |
| | |
This was hitting the file resource not the file ruby class.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| |/
|/| |
Fix chefstyle violations.
|
|/
|
|
| |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
|
|
|
| |
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>
|
| | | |
|