clintoncwolfe

[cwolfe@lodi profiles]$ be inspec archive arch-stack --overwrite -o arch-stack-try.tar.gz
Dependencies for profile arch-stack successfully vendored to /Users/cwolfe/sandbox/inspec/inspec-incident/profiles/arch-stack/vendor
I, [2019-10-15T15:55:44.017058 #75183]  INFO -- : Checking profile in arch-stack
W, [2019-10-15T15:55:44.017207 #75183]  WARN -- : Missing profile summary in inspec.yml
W, [2019-10-15T15:55:44.017249 #75183]  WARN -- : Missing profile maintainer in inspec.yml
W, [2019-10-15T15:55:44.017283 #75183]  WARN -- : Missing profile copyright in inspec.yml
W, [2019-10-15T15:55:44.017301 #75183]  WARN -- : Missing profile license in inspec.yml
I, [2019-10-15T15:55:44.017421 #75183]  INFO -- : Metadata OK.
[2019-10-15T15:55:44-04:00] WARN: DEPRECATION: The 'default' option for attributes is being replaced by 'value' - please use it instead. attribute name: 'Inspec::Input' (used at /Users/cwolfe/.inspec/cache/ef57e64b2a52366f52fa235d30832bdb7fa329c0bbebb422a64920561706d29c/controls/translated-controls.

clintoncwolfe

[cwolfe@lodi profiles]$ be inspec archive arch-stack --overwrite -o arch-stack-try.tar.gz
Dependencies for profile arch-stack successfully vendored to /Users/cwolfe/sandbox/inspec/inspec-incident/profiles/arch-stack/vendor
I, [2019-10-15T15:55:44.017058 #75183]  INFO -- : Checking profile in arch-stack
W, [2019-10-15T15:55:44.017207 #75183]  WARN -- : Missing profile summary in inspec.yml
W, [2019-10-15T15:55:44.017249 #75183]  WARN -- : Missing profile maintainer in inspec.yml
W, [2019-10-15T15:55:44.017283 #75183]  WARN -- : Missing profile copyright in inspec.yml
W, [2019-10-15T15:55:44.017301 #75183]  WARN -- : Missing profile license in inspec.yml
I, [2019-10-15T15:55:44.017421 #75183]  INFO -- : Metadata OK.
[2019-10-15T15:55:44-04:00] WARN: DEPRECATION: The 'default' option for attributes is being replaced by 'value' - please use it instead. attribute name: 'Inspec::Input' (used at /Users/cwolfe/.inspec/cache/ef57e64b2a52366f52fa235d30832bdb7fa329c0bbebb422a64920561706d29c/controls/translated-controls.

clintoncwolfe

Thank you for the contribution! However, your code currently does not pass our 
coding standard, which is enforced by RuboCop. If RuboCop does not like the code,
it will fail CI tests, such as TravisCI and Appveyor.

To check your code locally, run:
```
$ bundle exec rubocop
```

To auto-correct, run:

clintoncwolfe

As this appears to have an answer, and has had no activity for a while, I'm going to close
this issue. If you have further discussion for this topic, please feel free to re-open.

clintoncwolfe

Hi! Thanks so much for reporting this.  However, the functionality you describe is actuually handled by 
an underlying library, [train](https://github.com/inspec/train), which is used to detect platforms and
connect to remote scanning targets. Any new features or fixes would need to be contributed there, so 
please disuss on Train in a [new issue](https://github.com/inspec/train/issues/new).  Thanks again! 

clintoncwolfe

Thank you for your contribution! However, before we can accept it, we ask that you sign your commits, to indicate that you are the author of the code and that it otherwise meets the terms of our [Developer Certification of Origin](https://github.com/inspec/inspec/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco) policy.

After you have read the DCO, please sign your code, as follows:
```
git commit --amend -s
git push -f
```

Thank you!

clintoncwolfe

# UNOFFICAL - FOR DISCUSSION ONLY

# Test inspec under conditions in which it is unable to perform checks.

# NOTE: many of these mention doing "negative tests"  Here's an example:
# describe file('/this/does/not/exist') do
#   its('contents') { should_not include 'bananas'}
# end
#
# Depending on the particular resource, in InSpec 2.3.13, that test may fail, skip, or pass.

clintoncwolfe

I really like the idea of generating properties (and possibly even matchers) from the AWS API.  However, the InSpec project puts a high priority on maintaining a UX that is accessible to auditors.  That has a few consequences:

 * On plural resources, properties should be plural as well, for fluent reading.  It's easier to understand that `instance_ids` is a list, because it is plural.  You might be able to automate this conversion to plural; I'm sure there is a rubygem that can do that.
 *  The property names should be "fluent".  An AWS API method may be named oddly, perhaps exposing an implementation detail, or have a historical name.   Our audience generally is not familiar with the AWS API (and we should not ask them to be), and are expecting us to provide an interface that is fluent for their use as an InSpec user.  You may be able to generate all properties / matchers, then alias certain ones to be more fluent.
 * When it comes to docs, we are obliged to document each property and matcher that we suppor

clintoncwolfe

DEVOPS WEEKLY
ISSUE #346 - 13th August 2017

Some solid advanced topics this week, with in-depth articles on packaging, code repository organisation and observability, and a discussion of immutable infrastructure featuring yours truly.

Sponsor
======

Being on-call sucks - but is it getting better? See what 800+ professionals have to say about being on-call in VictorOps’ annual “State of On-Call” report.

clintoncwolfe

Keybase proof

I hereby claim:

• I am clintoncwolfe on github.
• I am clintoncwolfe (https://keybase.io/clintoncwolfe) on keybase.
• I have a public key ASCLwPLe9xbscLOqvRORhKPiZBtYwL0ddyWtCACWFUsu9Ao

To claim this, I am signing this object: