## New Features

- One's Option: `inspec exec` now 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 `--input` option 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](https://github.com/dmgasper) for this!
- Slowly but Surely: InSpec now is ready to accept the `input` option 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.

## Improvements

- 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
    - See `inspec plugin list -h` for more information
- Heads Up: The `inspec` check command will now issue a warning if the `inspec_version` constraint in a profile cannot be satisfied by the current version of InSpec running it.

## Bug Fixes

- Entirely Set: Resources were not fully initialized in some cases, which lead to broken messaging during reporting, but we fixed this.