* Remove any "All Rights Reserved" references
InSpec is licensed and released under the Apache 2.0 license. This
change removes all reference to legacy code files that still had
any Copyright or License lines referring to "All Rights Reserved".
Signed-off-by: Adam Leff <adam@leff.co>
* fix functional tests
Signed-off-by: Christoph Hartmann <chris@lollyrock.com>
Basically make sure everyone understands these are only subcommands. we might consider adding plugins for options or existing commands instead of new subcommands. this just ensures everyone knows what registry is for
only load plugins through the binary, never through the library. This avoids issue we have in accidentally loading plugins in tests and integration work. They should only be loaded when users request them.
When invoking inspec using ```inspec exec PATH```, the script always
exits with a 0 status code. This pull request proposes to exit with the
same status code as the Inspec Runner. This behavior is consistent with
how testing platforms of this type typically work.
Because of the way per-command arguments are handled, this is a little
different from the way e.g. kitchen handles it: any inspec command can
take the flag `--diagnose` to have it dump configuration first.
This add support for a JSON configuration file, where both
inspec detect --json-config=config.json
and
inspec detect --json-config=- <config.json
allow for reading the JSON config. There is no validation of its keys
in place.
Align with options in train. This also prevents unexpected behavior where sudo is used, without being requested. Example:
```
command('uname -a')
```
This command will not run if no sudo information is given and e.g. a sudo password is configured on the node. The user can activate sudo usage with `--sudo` now.
