inspec/docs
John Snow bdf1b01af7 Make changes to doc after review
Signed-off-by: John Snow <thelunaticscripter@outlook.com>
2019-07-22 17:09:09 -04:00
..
dev Mission-critical extra newline fix 2019-06-06 15:26:37 -04:00
resources Merge pull request #4269 from shoekstra/users_docs_example 2019-07-08 12:03:22 -07:00
shared fix ident in cmp matcher docs 2017-03-02 12:28:50 +01:00
.gitignore ignore auto-generated docs 2016-09-22 16:47:54 +02:00
config.md Update software name from InSpec to Chef Inspec 2019-04-29 15:16:56 -04:00
dsl_inspec.md Update software name from InSpec to Chef Inspec 2019-04-29 15:16:56 -04:00
dsl_resource.md Update software name from InSpec to Chef Inspec 2019-04-29 15:16:56 -04:00
glossary.md copyedit feedback 2019-06-06 12:50:19 -04:00
habitat.md Make changes to doc after review 2019-07-22 17:09:09 -04:00
inputs.md Replace semicolon 2019-06-12 12:12:27 -04:00
inspec_and_friends.md Update software name from InSpec to Chef Inspec 2019-04-29 15:16:56 -04:00
matchers.md Update software name from InSpec to Chef Inspec 2019-04-29 15:16:56 -04:00
migration.md Update software name from InSpec to Chef Inspec 2019-04-29 15:16:56 -04:00
platforms.md GCP InSpec Docs 2019-05-21 16:45:02 -07:00
plugin_kitchen_inspec.md Update software name from InSpec to Chef Inspec 2019-04-29 15:16:56 -04:00
plugins.md Update software name from InSpec to Chef Inspec 2019-04-29 15:16:56 -04:00
profiles.md Missed one 2019-06-05 12:06:08 -04:00
README.md Update software name from InSpec to Chef Inspec 2019-04-29 15:16:56 -04:00
reporters.md Update software name from InSpec to Chef Inspec 2019-04-29 15:16:56 -04:00
shell.md Add CLI target examples for Windows domain users 2019-06-25 15:34:51 -07:00
style.md Update software name from InSpec to Chef Inspec 2019-04-29 15:16:56 -04:00

Chef InSpec documentation

This is the home of the Chef 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 Chef InSpec resource will indicate its stability. As Chef 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