| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Adding files for onboarding the project to SonarQubes
|
|/
|
|
| |
Signed-off-by: Vinay Satish <vinay.satish@progress.com>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Updating files to account for Proxifier2
|
|/
|
|
| |
Signed-off-by: John <john.mccrae@progress.com>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
|
| |
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>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Calling yajl parser only once
|
| |
| |
| |
| | |
Signed-off-by: Renato Covarrubias <rnt@rnt.cl>
|
| | |
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|\
| |
| | |
Update rubocop-performance requirement from 1.15.0 to 1.15.2
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.0...v1.15.2)
---
updated-dependencies:
- dependency-name: rubocop-performance
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|\ \
| |/
|/| |
Darwin virtualization plugin: fix potential for false positive
|
| |
| |
| |
| | |
Signed-off-by: Jared Weyer <v-jaredweyer@microsoft.com>
|
| |
| |
| |
| | |
Signed-off-by: Jared Weyer <v-jaredweyer@microsoft.com>
|
|/
|
|
| |
Signed-off-by: Jared Weyer <v-jaredweyer@microsoft.com>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Fix linter error
|
|/
|
|
|
|
|
| |
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>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Update rubocop-performance requirement from 1.14.3 to 1.15.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.14.3...v1.15.0)
---
updated-dependencies:
- dependency-name: rubocop-performance
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Fall back to /proc/cpuinfo if lscpu doesn't have CPU totals
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Update rubocop-performance requirement from 1.14.2 to 1.14.3
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.14.2...v1.14.3)
---
updated-dependencies:
- dependency-name: rubocop-performance
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Bump actions/checkout from 2 to 3
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bumps [actions/checkout](https://github.com/actions/checkout) from 2 to 3.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/v2...v3)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| | |
| | |
| | |
| | | |
Obvious fix; these changes are the result of automation not creative thinking.
|
| | |
| | |
| | |
| | |
| | | |
* Add additional SUSE and openSUSE platforms - micro, hpc
Signed-off-by: jamesongithub@users.noreply.github.com <jamesongithub@users.noreply.github.com>
|
| | |
| | |
| | |
| | | |
Obvious fix; these changes are the result of automation not creative thinking.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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>
|