mirror of
https://github.com/inspec/inspec
synced 2024-11-10 23:24:18 +00:00
041f64a87f
* New matcher 'be_in' Fixes #2018 Signed-off-by: Rony Xavier <rx294@nyu.edu> * small fixes to wording. Signed-off-by: Aaron Lippold <lippold@gmail.com> * Added code to use be_in for with the following use case: describe nginx do its(module_list) { should be_in AUTHORIZED_MODULE_LIST } end Fixes #2018 Signed-off-by: Rony Xavier <rx294@nyu.edu> * Updates to the matcher Fixes #2018 Signed-off-by: Rony Xavier <rx294@nyu.edu> * Added tests for the be_in matcher Signed-off-by: Rony Xavier <rx294@nyu.edu> * Requested updates completed Signed-off-by: Rony Xavier <rx294@nyu.edu> |
||
|---|---|---|
| .. | ||
| 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