Hello InSpec friends!
We are delighted to announce the availability of version 4.16.0 of Chef InSpec. Changes include:
- One's Option:
inspec execnow supports a new CLI option,
--input name=value, which allows you to set an Input directly on the command line. While YAML files are still more practical and recommended for large numbers of inputs, use the
--inputoption to set just one or two.
- Mail Me Maybe: Manage your Postfix mail transfer agent configurations with its new available resource. Thank you to @dmgasper for this!
- Slowly but Surely: InSpec now is ready to accept the
inputoption from the audit cookbook and the kitchen-inspec plugin. This is another step on the journey of renaming 'attributes' to 'inputs'! You can use this immediately with kitchen-inspec, and stay tuned for the audit cookbook update!
- All in One Place: InSpec and Train plugins may now store configuration data in the user configuration file at
~/.inspec/config.json. This change allows plugins to store things like authentication tokens, service discovery addresses, or other information in one place. Plugins are not required to use the configuration file, but it is one option.
- Check It Out!: We improved the output of inspec plugin list:
- The output is now in a table format and includes built-in plugins
- Installed plugins now display their versions
- Filter which plugins to list via new CLI options
inspec plugin list -hfor more information
- Heads Up: The
inspeccheck command will now issue a warning if the
inspec_versionconstraint in a profile cannot be satisfied by the current version of InSpec running it.
- Entirely Set: Resources were not fully initialized in some cases, which lead to broken messaging during reporting, but we fixed this.
Get the Build
You can download binaries directly from downloads.chef.io.