Add json-file location to README #270
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add the location of the json-file output to the README so people don't have to go a-huntin' through the code to find the location. Signed-off-by: Adam Leff <adam@leff.co>
Since InSpec is included with the Chef omnibus build, we don't need to check the version matches the chef attributes since it defaults to nil. Signed-off-by: Adam Leff <adam@leff.co>
iennae
approved these changes
Aug 29, 2017
arlimus
approved these changes
Aug 29, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add the location of the json-file output to the README so people don't
have to go a-huntin' through the code to find the location.
Also fix a test that's failing in Travis due to the InSpec version being embedded in Chef omnibus since Chef 13.
Fixes #269