mirror of
https://github.com/inspec/inspec
synced 2024-11-23 21:23:29 +00:00
175c3e1189
* adding database.xml with attributes to files and mocking it in the helper.rb Signed-off-by: Vern Burton <me@vernburton.com> * adding logic to test class returned by XPATH and using functions from respective classes to fill a array for return, and unit and integration tests to ensure functionality Signed-off-by: Vern Burton <me@vernburton.com> * updating docs to show how attributes are used Signed-off-by: Vern Burton <me@vernburton.com> * 'and' instead of 'or' makes more sense Signed-off-by: Vern Burton <me@vernburton.com> * adding default else for capturing unknown classes from REXML Signed-off-by: Vern Burton <me@vernburton.com> * removing extra newline Signed-off-by: Vern Burton <me@vernburton.com> * adding fail case with enough information to debug in future case Signed-off-by: Vern Burton <me@vernburton.com> |
||
|---|---|---|
| .. | ||
| resources | ||
| shared | ||
| .gitignore | ||
| dsl_inspec.md | ||
| dsl_resource.md | ||
| habitat.md | ||
| inspec_and_friends.md | ||
| matchers.md | ||
| migration.md | ||
| plugin_kitchen_inspec.md | ||
| profiles.md | ||
| README.md | ||
| ruby_usage.md | ||
| shell.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:
- Auto-generating docs from code
- Transforming markdown+snippets in this folder into pure markdown in
www/source/docs - 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 versionsStability: Stable- API is well established and proofed. Maintaining compatibility is a high priorityStability: Locked- Only security and performance fixes are allowed