mirror of
https://github.com/inspec/inspec
synced 2024-11-23 13:13:22 +00:00
Update docs/habitat.md
Co-Authored-By: Jerry Aldrich <aldrich003@gmail.com>
This commit is contained in:
parent
d223f63be5
commit
ea8c76dcd2
1 changed files with 1 additions and 1 deletions
|
@ -24,7 +24,7 @@ After creating a Chef Habitat package for an Chef InSpec profile (see CLI comman
|
|||
hab start adamleff/inspec-profile-frontend1
|
||||
```
|
||||
|
||||
The Chef Habitat Supervisor will install Chef InSpec and execute your profile in a loop. The loop is controled by two variables the `interval` and the `splay`. The `interval` is a set time you want inspec to run the default is `1800` seconds. The `splay` is a random generated sleep time so that if you don't have a thundering herd scenario when sending your report to an exernal server like Chef Automate. The defualt for the `splay` is also 1800. You can also set the `splay_first_run` so that when your habitat package is started or updated it will wait a random period of time between 0 and the number set for the `splay_first_run` before running InSpec. The default of the `splay_first_run` is 0.
|
||||
The Chef Habitat Supervisor will install Chef InSpec and execute your profile in a loop. The loop is controled by two variables the `interval` and the `splay`. The `interval` is a set time you want InSpec to run (the default is `1800` seconds). The `splay` is a randomly generated sleep time so that if you don't have a thundering herd scenario when sending your report to an external server like Chef Automate. The default for the `splay` is also `1800` seconds. You can also set the `splay_first_run` so that when your Habitat package is started or updated it will wait a random period of time between 0 and the number set for the `splay_first_run` before running InSpec. The default of the `splay_first_run` is `0` seconds.
|
||||
|
||||
```bash
|
||||
HAB_INSPEC_PROFILE_FRONTEND1="interval = 60" hab start adamleff/inspec-profile-frontend1
|
||||
|
|
Loading…
Reference in a new issue