0eafbd945c
We store validated `map.jinja` dump under the profile `files`
directory to access them with `inspec.profile.file('filename')` to
validate the content of the generated mapdata file.
The YAML files contain a value specific to each minion, its hostname,
so we use string format to expand `%{hostname}`.
The `default` inspec profile need to depends on `share` to access the
`system` and `salt_minion` libraries.
|
||
|---|---|---|
| .. | ||
| controls | ||
| files/mapdata | ||
| inspec.yml | ||
| README.md | ||
InSpec Profile:
default
This shows the implementation of the default InSpec profile.
Verify a profile
InSpec ships with built-in features to verify a profile structure.
$ inspec check default
Summary
-------
Location: default
Profile: profile
Controls: 4
Timestamp: 2019-06-24T23:09:01+00:00
Valid: true
Errors
------
Warnings
--------Execute a profile
To run all supported controls on a local machine use
inspec exec /path/to/profile.
$ inspec exec default
..
Finished in 0.0025 seconds (files took 0.12449 seconds to load)
8 examples, 0 failuresExecute a specific control from a profile
To run one control from the profile use
inspec exec /path/to/profile --controls name.
$ inspec exec default --controls package
.
Finished in 0.0025 seconds (files took 0.12449 seconds to load)
1 examples, 0 failuresSee an example control here.