As raised in #1526, adding an additional example showing how
a user can use the `where` accessor to find commands matching
a pattern and write a test using the results.
Signed-off-by: Adam Leff <adam@leff.co>
The following new resources have been added; however, they
presently only support FreeBSD and similar.
* `zfs_dataset`: tests if a named ZFS dataset is present
and/or has certain properties.
* `zfs_pool`: tests if a named ZFS pool is present and/or
has certain properties.
Additionally, the `mount` resource has been reworked to
include support for FreeBSD; while the existing class
was renamed to LinuxMountParser.
Unit-tests were added for all of the above.
Signed-off-by: Joseph Benden <joe@benden.us>
The crontab resource parses a particular user's crontab file into
individual entries and allows the user to assert information about
each entry as needed.
Signed-off-by: Adam Leff <adam@leff.co>
* Fixes the npm package example to state 'npm' vs 'gem'
* Fixes powershell resource to specify the resource instead of 'script'
* Updates the example to rename variable 'script'
While ruby would allow the local variable and the presence of the InSpec method at the same time I think that it is bad form. Other resource examples also use 'script'.
* Changes pip to show generic example
Other package like resources show a generic example in the default.
Signed-off-by: Franklin Webber <franklin@chef.io>
The html rendered from markdown would look like:
`<h3>be<em>grouped</em>into</h3>`
When there is only one `_` the html rendered correctly:
`<h3>be_directory</h3>`
This change escapes the `_` when there are multiple.
* New markdown: `### be\_grouped\_into`
* New html: `<h3>be_grouped_into</h3>`
resource matchers fixed:
* be_block_device
* be_character_device
* be_grouped_into
* be_linked_to
* be_owned_by
* have_app_pool
* have_property_value
resource fixed:
* parse_config_file
Signed-off-by: Nathen Harvey <nharvey@chef.io>
