summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* hostname: Improve the windows reboot messagehostname_rebootTim Smith2020-05-281-1/+2
| | | | | | Make sure this works in cinc Signed-off-by: Tim Smith <tsmith@chef.io>
* Merge pull request #9928 from chef/hostname_solarisTim Smith2020-05-281-18/+4
|\ | | | | hostname: Remove support for Solaris 5.10
| * Add header to the hostname filehostname_solarisTim Smith2020-05-281-0/+3
| | | | | | | | Signed-off-by: Tim Smith <tsmith@chef.io>
| * hostname: Remove support for Solaris 5.10Tim Smith2020-05-281-18/+1
| | | | | | | | | | | | 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>
* | Merge pull request #9931 from chef/cron_access_scopeTim Smith2020-05-281-2/+2
|\ \ | | | | | | Make sure file is properly scoped in cron_access
| * | Make sure file is properly scoped in cron_accessTim Smith2020-05-281-2/+2
|/ / | | | | | | | | | | This was hitting the file resource not the file ruby class. Signed-off-by: Tim Smith <tsmith@chef.io>
* | Bump version to 16.2.4 by Chef Expeditorv16.2.4Chef Expeditor2020-05-297-19/+20
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Merge pull request #9929 from chef/fix-chefstyleTim Smith2020-05-281-4/+4
|\ \ | |/ |/| Fix chefstyle violations.
| * Fix chefstyle violations.Pete Higgins2020-05-281-4/+4
|/ | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
* changed according to suggestion of @phigginsaklyachkin2020-05-281-10/+8
| | | | Signed-off-by: aklyachkin <aklyachkin@gmail.com>
* support for AIX and Solaris in cron_allow resourceaklyachkin2020-05-281-3/+13
| | | | Signed-off-by: aklyachkin <aklyachkin@gmail.com>
* Bump version to 16.2.3 by Chef Expeditorv16.2.3Chef Expeditor2020-05-287-19/+20
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #9926 from chef/docsTim Smith2020-05-288-12/+74
|\ | | | | Improve auto-generated docs
| * Add example to plistTim Smith2020-05-281-0/+11
| | | | | | | | Signed-off-by: Tim Smith <tsmith@chef.io>
| * Improve auto-generated docsTim Smith2020-05-288-12/+63
|/ | | | | | | | 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>
* Bump version to 16.2.2 by Chef Expeditorv16.2.2Chef Expeditor2020-05-287-19/+20
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #9925 from jaymzh/remote_file_ssl2Tim Smith2020-05-272-7/+16
|\ | | | | Update to ssl_verify_mode on remote_file
| * Update to ssl_verify_mode on remote_filePhil Dibowitz2020-05-272-7/+16
|/ | | | | | | | | | | | | | | 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>
* Bump version to 16.2.1 by Chef Expeditorv16.2.1Chef Expeditor2020-05-287-19/+20
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #9923 from chef/docs_updatesTim Smith2020-05-279-34/+45
|\ | | | | Update & add resource descriptions for documentation generation
| * Fix incorrect ruby in the ssl_verify_mode checkTim Smith2020-05-271-2/+2
| | | | | | | | Signed-off-by: Tim Smith <tsmith@chef.io>
| * Chefstyle updatesTim Smith2020-05-273-3/+2
| | | | | | | | Signed-off-by: Tim Smith <tsmith@chef.io>
| * Update ssl_verify_mode to have a type and an introduced valueTim Smith2020-05-271-1/+2
| | | | | | | | Signed-off-by: Tim Smith <tsmith@chef.io>
| * Update & add resource descriptions for documentation generationTim Smith2020-05-277-30/+41
|/ | | | | | Improve the docs we auto generate. Signed-off-by: Tim Smith <tsmith@chef.io>
* Merge pull request #9921 from Xorima/patch-1Tim Smith2020-05-271-1/+10
|\ | | | | CHEF_MVPS for 2019
| * Add Joshua's accountJason Field2020-05-271-1/+1
| | | | | | Signed-off-by: Jason Field <jason@avon-lea.co.uk>
| * Fix markdown alignmentJason Field2020-05-271-8/+7
| |
| * CHEF_MVPS for 2019Jason Field2020-05-271-1/+11
|/ | | | | Adding ChefMVPs from 2019 Signed-off-by: Jason Field <jason@avon-lea.co.uk>
* Bump version to 16.2.0 by Chef Expeditorv16.2.0Chef Expeditor2020-05-277-19/+20
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 16.1.19 by Chef Expeditorv16.1.19Chef Expeditor2020-05-277-19/+20
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #9833 from jaymzh/remote_file_sslTim Smith2020-05-275-1/+51
|\ | | | | Add ssl_verify option for remote_file
| * Add ssl_verify option for remote_filePhil Dibowitz2020-05-185-1/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | Bump version to 16.1.18 by Chef Expeditorv16.1.18Chef Expeditor2020-05-277-19/+20
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Merge pull request #9910 from chef/add-input-property-to-executeTim Smith2020-05-273-6/+543
|\ \ | | | | | | Add an input property to the execute resource for passing input on STDIN
| * | Escape interpolation in code examples.add-input-property-to-executePete Higgins2020-05-261-13/+13
| | | | | | | | | | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
| * | Add an example using the input property.Pete Higgins2020-05-261-0/+6
| | | | | | | | | | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
| * | Add examples for execute resource.Pete Higgins2020-05-261-0/+521
| | | | | | | | | | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
| * | Reformat description and add note.Pete Higgins2020-05-261-4/+9
| | | | | | | | | | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
| * | Fix property definition according to PR feedback.Pete Higgins2020-05-261-2/+2
| | |
| * | Fix a small style inconsistency.Pete Higgins2020-05-261-1/+1
| | | | | | | | | | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
| * | Add an input property to the execute resource for passing input on STDIN.Pete Higgins2020-05-262-1/+6
| | | | | | | | | | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
* | | Merge pull request #9896 from damacus/resource/homebrew_updateTim Smith2020-05-273-0/+138
|\ \ \ | | | | | | | | Adds the homebrew_update resource
| * | | Adds the homebrew_update resourceDan Webb2020-05-213-0/+138
| | | | | | | | | | | | | | | | Signed-off-by: Dan Webb <dan.webb@damacus.io>
* | | | Update CHANGELOG.md to reflect the promotion of 16.1.16Chef Expeditor2020-05-272-18/+22
| | | | | | | | | | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | | | Merge pull request #9917 from chef/16116_notesTim Smith2020-05-261-0/+16
|\ \ \ \ | | | | | | | | | | Add 16.1.16 release notes
| * | | | Update RELEASE_NOTES.md Tim Smith2020-05-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Tim Smith <tsmith@chef.io> Co-authored-by: Ian Maddaus <IanMadd@users.noreply.github.com>
| * | | | Add 16.1.16 release notes16116_notesTim Smith2020-05-261-0/+16
|/ / / / | | | | | | | | | | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* | | | Bump version to 16.1.17 by Chef Expeditorv16.1.17Chef Expeditor2020-05-277-19/+20
| | | | | | | | | | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | | | Merge pull request #9890 from chef/lcg/resource_name_fixesLamont Granquist2020-05-262-10/+15
|\ \ \ \
| * | | | Chef-16.2 breaking changelcg/resource_name_fixesLamont Granquist2020-05-202-10/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
View Lorry Controller Status