Mirrors/inspec
2
0
Fork 0
mirror of https://github.com/inspec/inspec synced 2024-11-27 07:00:39 +00:00
Code Issues Projects Releases Packages Wiki Activity
inspec/docs
History
Nathen Harvey 7e4157ddf4 Headers and list elements that include more than one _ character were being rendered incorrectly. (Perhaps it is only when there are an even number but in any case I only found words with either one or two _s.) 
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>
2016-10-20 07:07:18 -04:00
..
resources Headers and list elements that include more than one _ character were being rendered incorrectly. (Perhaps it is only when there are an even number but in any case I only found words with either one or two _s.) 2016-10-20 07:07:18 -04:00
shared add all partials for resources 2016-09-22 15:23:21 +02:00
.gitignore ignore auto-generated docs 2016-09-22 16:47:54 +02:00
dsl_inspec.md Fix a few typos 2016-09-27 22:02:20 -04:00
dsl_resource.md update docs to markdown 2016-09-22 10:16:16 +02:00
inspec_and_friends.md add intro to inspec and friends 2016-09-26 06:21:05 +02:00
matchers.md update docs to markdown 2016-09-22 10:16:16 +02:00
plugin_kitchen_inspec.html.md update docs to markdown 2016-09-22 10:16:16 +02:00
profiles.md update dependency documentation and mention the lockfile 2016-09-26 16:31:06 +01:00
README.md generate docs for cli 2016-09-22 13:43:57 +02:00
ruby_usage.md add ruby usage in inspec as markdown 2016-09-22 15:06:04 +02:00
shell.md update docs to markdown 2016-09-22 10:16:16 +02:00

README.md

InSpec documentation

This is the home of the InSpec documentation. This documentation provides an introduction to this mechanism and shows how to write custom tests.

The goal of this folder is for any community member to clone these docs, make the changes, check if they are valid, and contribute to the project.

How to build docs

We build docs by:

  1. Auto-generating docs from code
  2. Transforming markdown+snippets in this folder into pure markdown in www/source/docs
  3. Rendering them to the website via instructions in www/

For development, you only need step 1!

1 Generate docs

To generate all docs run:

bundle exec rake docs

You can run tasks individually. For a list of tasks run:

bundle exec rake --tasks docs

Stability Index

Every available InSpec resource will indicate its stability. As InSpec matures, certain parts are more reliable than others. Brand new features are likely to be redesigned and marked as such.

The stability indices are as follows:

  • Stability: Deprecated - This features will be removed in future versions, because its known for being problematic. Do not rely on it.
  • Stability: Experimental - New features may change or are removed in future versions
  • Stability: Stable - API is well established and proofed. Maintaining compatibility is a high priority
  • Stability: Locked - Only security and performance fixes are allowed