summaryrefslogtreecommitdiff
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
* Bump version to 18.1.5 by Chef ExpeditorHEADv18.1.5mainChef Expeditor2023-04-061-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 18.1.4 by Chef Expeditorv18.1.4Chef Expeditor2023-03-281-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Add support for macOS Rapid Security Response updates (#1788)Nathaniel Strauss2023-03-281-1/+3
| | | | | | | | | | | | | | | | | Apple is adding a new update type to macOS called Rapid Security Responses. These updates change the build version, but not the OS version reported by `sw_vers`. Instead, a new `ProductVersionExtra` key is returned to denote a specific supplemental version only when a RSR is installed. If no RSR is installed the key is not present. ``` $ sw_vers ProductName: macOS ProductVersion: 13.3 ProductVersionExtra: (a) BuildVersion: 22E7752300f ``` https://support.apple.com/guide/deployment/rapid-security-responses-dep93ff7ea78/web This PR adds support for reporting on the RSR version when a patch is installed. The information is important to Mac admins since it gives a full picture of current OS build, whether a security vulnerability has been patched, and, depending on Apple's future plans, if there is functionality change which could impact Chef. I'll admit the spec test isn't totally useful, especially since most machines running tests likely won't have an RSR, but it does match real world scenarios. Signed-off-by: nstrauss <nathaniel.strauss@gusto.com>
* Bump version to 18.1.3 by Chef Expeditorv18.1.3Chef Expeditor2023-03-081-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 18.1.2 by Chef Expeditorv18.1.2Chef Expeditor2023-02-281-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* [block_device] Record firmware revision of nvme block devices (#1787)Saravanan D2023-02-281-1/+1
| | | | | Enhancing the plugin to record the firmware of nvme block devices whose sysfs endpoint differs from HDD Signed-off-by: Saravanan D <saravanand@fb.com>
* Bump version to 18.1.1 by Chef Expeditorv18.1.1Chef Expeditor2023-02-211-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #1786 from rnt/fix/calling-yajl-parser-only-onceJohn McCrae2023-02-216-94/+103
|\ | | | | Calling yajl parser only once
| * fix: CAlling only once YAJL parserRenato Covarrubias2023-02-176-94/+103
| |
* | Bump version to 18.1.0 by Chef Expeditorv18.1.0Chef Expeditor2023-02-201-1/+1
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Update rubocop-performance requirement from 1.15.2 to 1.16.0 (#1784)dependabot[bot]2023-02-2012-20/+20
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Update rubocop-performance requirement from 1.15.2 to 1.16.0 Updates the requirements on [rubocop-performance](https://github.com/rubocop/rubocop-performance) to permit the latest version. - [Release notes](https://github.com/rubocop/rubocop-performance/releases) - [Changelog](https://github.com/rubocop/rubocop-performance/blob/master/CHANGELOG.md) - [Commits](https://github.com/rubocop/rubocop-performance/compare/v1.15.2...v1.16.0) --- updated-dependencies: - dependency-name: rubocop-performance dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> * Fix chefstyle linting errors Signed-off-by: Neha Pansare <neha.pansare@progress.com> * Fix unit test failures due to changing match with include? to fix chefstye error. This happens because method file_val_if_exists returns string only when file is found, else it returns nil Signed-off-by: Neha Pansare <neha.pansare@progress.com> --------- Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Neha Pansare <neha.pansare@progress.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Neha Pansare <neha.pansare@progress.com>
* Bump version to 18.0.27 by Chef Expeditorv18.0.27Chef Expeditor2023-02-141-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Add cloud provider oci (#1780)Renato Covarrubias2023-02-143-0/+185
| | | | | ohai cloud fail if the vm is in Oracle Cloud Infrastructure (OCI). This PR add support to this cloud provider to cloud plugin. It also adds OCI detection to the cloud plugin. Signed-off-by: Renato Covarrubias <rnt@rnt.cl>
* Force encoding with timezones that include umlauts if zone encoding is ↵tpowell-progress2023-01-252-0/+35
| | | | | | | | | IBM437 (#1781) * If time.zone is encoded in Encoding::IBM437, force to WINDOWS_1252 * Added description of what's going on with the force/encode chain * Handle umlauts in popen output from Mixlib shellout Signed-off-by: Thomas Powell <powell@progress.com>
* cookstyle changesJared Weyer2023-01-041-3/+2
| | | | Signed-off-by: Jared Weyer <v-jaredweyer@microsoft.com>
* account for situtaion in which parallels is installed on a VMJared Weyer2022-12-141-8/+6
| | | | Signed-off-by: Jared Weyer <v-jaredweyer@microsoft.com>
* Bump version to 18.0.26 by Chef Expeditorv18.0.26Chef Expeditor2022-10-111-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Fix linter errorMarc A. Paradise2022-10-111-2/+1
| | | | | | | Makes this function a one-liner too, because the return is implicit and the evaluation of the conditionals will yield true or false. Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
* Bump version to 18.0.25 by Chef Expeditorv18.0.25Chef Expeditor2022-10-111-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* [ohai][ec2][looks_like_ec2] Do not depend on metadata endpoint (#1768)Greg Batye2022-10-111-7/+1
| | | | | | | Do not depend metadata endpoint For environments where full tunnel VPN is used, requiring a connection to the local metadata endpoint causes node['cloud'] = nil. At a minimum node['cloud']['provided'] attribute should be populated even if metadata can not be fetched. Signed-off-by: Greg Batye <gbatye@gmail.com>
* Bump version to 18.0.24 by Chef Expeditorv18.0.24Chef Expeditor2022-09-201-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 18.0.23 by Chef Expeditorv18.0.23Chef Expeditor2022-09-061-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Use a minimum of 1 thread per core for CPU total calculation (#1756)Stan Hu2022-09-061-1/+2
| | | | | | | | | | In some LXD containers running with VT-x hardware virtualization, it appears that threads per core is 0, resulting in a total number of CPUs of 0. Add a test case and handle some quirks with the `lscpu` output. Closes https://github.com/chef/ohai/issues/1755 Signed-off-by: Stan Hu <stanhu@gmail.com>
* Bump version to 18.0.22 by Chef Expeditorv18.0.22Chef Expeditor2022-08-301-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #1761 from stanhu/sh-cpuinfo-fallbacktpowell-progress2022-08-301-4/+12
|\ | | | | Fall back to /proc/cpuinfo if lscpu doesn't have CPU totals
| * Fall back to /proc/cpuinfo if lscpu doesn't have CPU totalsStan Hu2022-08-241-4/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | https://github.com/chef/ohai/pull/1454 made `lscpu` the primary way Ohai gathers CPU data, but the parser doesn't handle the output from a Raspberry Pi 4 Cortex-A72. For example, an ARM cluster has the output `Core(s) per cluster` instead of `Core(s) per socket`. We should fall back to `/proc/cpuinfo` if we don't get reasonable data back. It's not enough just to have `lscpu` output. Closes https://github.com/chef/ohai/issues/1760 Signed-off-by: Stan Hu <stanhu@gmail.com>
* | Bump version to 18.0.21 by Chef Expeditorv18.0.21Chef Expeditor2022-08-231-1/+1
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Bump version to 18.0.20 by Chef Expeditorv18.0.20Chef Expeditor2022-08-091-1/+1
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Bump version to 18.0.19 by Chef Expeditorv18.0.19Chef Expeditor2022-08-091-1/+1
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Add additional SUSE and openSUSE platforms - micro, hpc (#1753)James Yang2022-08-091-1/+2
| | | | | | | | | | * Add additional SUSE and openSUSE platforms - micro, hpc Signed-off-by: jamesongithub@users.noreply.github.com <jamesongithub@users.noreply.github.com>
* | Bump version to 18.0.18 by Chef Expeditorv18.0.18Chef Expeditor2022-08-091-1/+1
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Fix FIPS mode detection (#1754)Stan Hu2022-08-091-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously FIPS detection relied on the `OpenSSL::OPENSSL_FIPS` constant being defined. However, on RedHat operating systems, this constant is always defined in `/usr/include/openssl/opensslconf-x86_64.h`. As a result, on such operating systems FIPS mode would erroneously be labeled as enabled. This constant is a necessary but not sufficient condition to determine whether FIPS is actually enabled. OpenSSL has a runtime `fips_mode` check (https://wiki.openssl.org/index.php/FIPS_mode()) that should be used instead. Ruby will use this if the `OPENSSL_FIPS` compile-time constant is available: https://github.com/ruby/ruby/blob/685efac05983dee44ce2d96c24f2fcb96a0aebe2/ext/openssl/ossl.c#L413-L428 Signed-off-by: Stan Hu <stanhu@gmail.com>
* | Bump version to 18.0.17 by Chef Expeditorv18.0.17Chef Expeditor2022-08-021-1/+1
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Do not attempt to reinitialize constantsBalasankar 'Balu' C2022-07-214-71/+79
|/ | | | Signed-off-by: Balasankar 'Balu' C <balu@dravidam.net>
* Bump version to 18.0.16 by Chef Expeditorv18.0.16Chef Expeditor2022-06-141-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 18.0.15 by Chef Expeditorv18.0.15Chef Expeditor2022-06-141-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 18.0.14 by Chef Expeditorv18.0.14Chef Expeditor2022-06-021-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #1747 from chef/jfm/ohai_ruby3.1John McCrae2022-06-021-3/+4
|\
| * Testing Ruby 3.1 supportJohn McCrae2022-04-201-3/+4
| | | | | | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
* | Bump version to 18.0.13 by Chef Expeditorv18.0.13Chef Expeditor2022-05-311-1/+1
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Merge pull request #1741 from mattp-/maintpowell-progress2022-05-311-3/+18
|\ \ | | | | | | networking/linux: map src only default routes accordingly
| * | prefer route that explicitly define a deviceMatt Phillips2022-05-161-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in theory I don't this should occur in real life, as I'm pretty sure /usr/sbin/ip should always print the dev routes above non dev routes if the metric is the same, but it is a good case to cover in code. also removed the default metric 10 gateway route as it was spurious/irrelevant to the test. Signed-off-by: Matt Phillips <mphillips81@bloomberg.net>
| * | networking/linux: map src only default routes accordinglyMatt Phillips2022-05-161-1/+12
| |/ | | | | | | | | | | | | | | | | | | | | | | in certain configurations a default route can be set via src only / not dev, but should still be accounted for in terms of calculating the 'favored' default route / what is chosen as ipaddress for a given node. This change augments the previously added changes to account for nexthop multipath routing; but only in scenarios src address is set but only in scenarios src address is set. Signed-off-by: Matt Phillips <mphillips81@bloomberg.net>
* | Bump version to 18.0.12 by Chef Expeditorv18.0.12Chef Expeditor2022-05-171-1/+1
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Bump version to 18.0.11 by Chef Expeditorv18.0.11Chef Expeditor2022-05-171-1/+1
|/ | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump version to 18.0.10 by Chef Expeditorv18.0.10Chef Expeditor2022-04-071-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Updating for Ruby 3.1John McCrae2022-04-061-1/+3
| | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
* Updating For Ruby 3.1John McCrae2022-04-066-6/+6
| | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
* Bump version to 18.0.9 by Chef Expeditorv18.0.9Chef Expeditor2022-03-161-1/+1
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* [mdadm] Record array UUID (#1742)Saravanan D2022-03-151-0/+2
| | | | | Useful to have the UUID of the arrays to assemble them when the need arises Signed-off-by: Saravanan D <saravanand@fb.com>
View Lorry Controller Status