diff options
| author | Phil Dibowitz <phil@ipom.com> | 2017-10-04 15:17:14 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-10-04 15:17:14 -0700 |
| commit | 978bcf908e9ac8321d79a1a55dd4d4c3e4c6666e (patch) | |
| tree | acefe3ac40f64f754a561d5a6c5f56e00eb4cb85 /RELEASE_NOTES.md | |
| parent | da3e87f8e1f84e60c96a38cdb9eaea2a42ac8b0c (diff) | |
| download | ohai-978bcf908e9ac8321d79a1a55dd4d4c3e4c6666e.tar.gz | |
Critical Plugins (#1064)
This adds a new Ohai configuration `critical_plugins` which will cause
Ohai to exit (or `fail` if inside of Chef) if the plugins in the list do
not run successfully.
This feature only supports Ohai 7-style named plugins, not the ancient
Ohai 6-style stuff.
Tests to follow, but:
```
$ cat /home/phild/ohai.rb
ohai.critical_plugins << :Filesystem
$ ./bin/ohai -c /home/phild/ohai.rb
[2017-10-03T13:43:14-07:00] INFO: The plugin path /etc/chef/ohai/plugins does not exist. Skipping...
[2017-10-03T13:43:14-07:00] ERROR: The following plugins marked as critical failed: [:Filesystem]
```
And when I run Chef:
```
[2017-10-03T13:44:11-07:00] FATAL: RuntimeError: The following plugins marked as critical failed: [:Filesystem2]. Failing Chef run.
```
This fixes #879.
Signed-off-by: Phil Dibowitz <phil@ipom.com>
Diffstat (limited to 'RELEASE_NOTES.md')
| -rw-r--r-- | RELEASE_NOTES.md | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md index 657a2911..5f53e49e 100644 --- a/RELEASE_NOTES.md +++ b/RELEASE_NOTES.md @@ -1,3 +1,13 @@ +# Unreleased + +### Critical Plugins + +Users can now specify a list of plugins which are `critical`. Critical plugins will cause Ohai to fail if they do not run successfully (and thus cause a Chef run using Ohai to fail). The syntax for this is: + +``` +ohai.critical_plugins << :Filesystem +``` + # Ohai Release Notes 13.5 ### Correctly detect IPv6 routes ending in :: |