summaryrefslogtreecommitdiff
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
* Add specs and rename fingerprint -> short idzypper_repositoryTim Smith2020-06-051-9/+12
| | | | | | | | These aren't actually fingerprints. They're short key ids https://futureboy.us/pgp.html#ShortKeyID Signed-off-by: Tim Smith <tsmith@chef.io>
* Change how we get the fingerprint againTim Smith2020-06-041-4/+4
| | | | | | It turns out the string I was matching on before was actually an error message to stderr. We can't rely on that. Signed-off-by: Tim Smith <tsmith@chef.io>
* Make sure gpg_version is actually a version objectTim Smith2020-06-041-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Fix zypper_repository key handling on SLES 15+Tim Smith2020-06-041-4/+21
| | | | | | | | gpg 2.2 changed the output without a major version bump. Now we need to get the gpg version and then shell out the appropriate command to determine the fingerprint. Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump version to 16.2.14 by Chef Expeditorv16.2.14Chef Expeditor2020-06-041-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 16.2.13 by Chef Expeditorv16.2.13Chef Expeditor2020-06-041-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #9946 from ↵Tim Smith2020-06-041-1/+5
|\ | | | | | | | | MsysTechnologiesllc/sangmeshA/9610-Fix_Powershell_Package_does_not_throw_error_when_it_cannot_connect_to_powershell_gallery Fixed Powershell_Package does not throw error when it cannot connect …
| * Fixed Powershell_Package does not throw error when it cannot connect to ↵sanga172020-06-021-1/+5
| | | | | | | | | | | | powershell gallery Signed-off-by: sanga17 <sausekar@msystechnologies.com>
* | Bump version to 16.2.12 by Chef Expeditorv16.2.12Chef Expeditor2020-06-041-1/+1
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Bump version to 16.2.11 by Chef Expeditorv16.2.11Chef Expeditor2020-06-041-1/+1
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | archive_file: move ffi-libarchive into a simple helper methodrequire_archive_fileTim Smith2020-06-031-6/+19
| | | | | | | | | | | | | | This way it always gets called in the action, but we can still avoid spec failures on systems that don't have ffi-libarchive Signed-off-by: Tim Smith <tsmith@chef.io>
* | Bump version to 16.2.10 by Chef Expeditorv16.2.10Chef Expeditor2020-06-031-1/+1
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Update lib/chef/resource/archive_file.rb Tim Smith2020-06-031-1/+1
| | | | | | | | | | | | | | :facepalm: Signed-off-by: Tim Smith <tsmith@chef.io> Co-authored-by: pete higgins <pete@peterhiggins.org>
* | archive_file: better handle mode property and deprecate Integer valuesfix_file_modeTim Smith2020-06-032-2/+13
|/ | | | | | | | | | | | | | | | FileUtils.mkdir_p expects the mode to be in octal form. We accept Integers, but Ruby doesn't have a way to tell if what the user passed was octal or not. The safest thing to do here is to only accept mode as a String and then convert it to octal form with .to_i(8). This adds a new deprecation and correctly sets the file mode value as octal. Right now this feature works like this: String mode: applies wrong permission Base 10 mode: applies wrong permissions Octal mode: Works New behavior: String mode: Works Base 10 mode: Works but throws a deprecation warning Octal mode: applies the wrong permissions and throws a deprecation warning Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump version to 16.2.9 by Chef Expeditorv16.2.9Chef Expeditor2020-05-301-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 16.2.8 by Chef Expeditorv16.2.8Chef Expeditor2020-05-291-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 16.2.7 by Chef Expeditorv16.2.7Chef Expeditor2020-05-291-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #9927 from chef/hostname_rebootTim Smith2020-05-281-1/+2
|\ | | | | hostname: Improve the windows reboot message
| * 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>
* | Bump version to 16.2.6 by Chef Expeditorv16.2.6Chef Expeditor2020-05-291-1/+1
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Bump version to 16.2.5 by Chef Expeditorv16.2.5Chef Expeditor2020-05-291-1/+1
|/ | | | Obvious fix; these changes are the result of automation not creative thinking.
* 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>
* | 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-291-1/+1
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | 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-281-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Add example to plistTim Smith2020-05-281-0/+11
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Improve auto-generated docsTim Smith2020-05-284-7/+57
| | | | | | | | 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-281-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* 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-281-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* 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-272-2/+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>
* Bump version to 16.2.0 by Chef Expeditorv16.2.0Chef Expeditor2020-05-271-1/+1
| | | | 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-271-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #9833 from jaymzh/remote_file_sslTim Smith2020-05-274-1/+31
|\ | | | | Add ssl_verify option for remote_file
| * Add ssl_verify option for remote_filePhil Dibowitz2020-05-184-1/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-271-1/+1
| | | | | | | | 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
| | |
View Lorry Controller Status