Initial Commit
IE-869: add attributes directory and default.rb attributes file
Merge pull request #1 in ITS/zero_cookbook from IE-869 to master

* commit '7d07796ab5990a1496f2b2085f5732dc1d732092':
  IE-869: add attributes directory and default.rb attributes file
UIS-263: modified metadata.rb; added default headers to attribute/recipe default.rb files.
Merge pull request #2 in ITS/zero_cookbook from UIS-263 to master

* commit 'f953691cd029a069e6efd371f7be62aaa10969c6':
  UIS-263: modified metadata.rb; added default headers to attribute/recipe default.rb files.
A polar bear ice fishing for data.
use dev-mode for chef_vault_item
kill stray bogus cert from testing
use chef-vault w/ data bag item loading fallback
corrected recipe name in comment
add upgrade recipe

Even though the newest (as of right now) release is set to install by
default, the attributes are set to 'upgrade' for splunk 4.3.7. This is
because internally, we use 4.2.1 and need to upgrade to 4.3.x before
we can upgrade to 6.0.1. Our internal splunk cookbook for 4.2.1 will
be used alongside this one until the upgrade is performed. This is
probably not a common use case, but the pattern is available for those
who want to reuse it. Simply set the appropriate attributes (see
`attributes/upgrade.rb`)
use dev mode for upgrade testing
add chefspec for (allthethings)
resolve rubocop, foodcritic findings
rubocop: class length

Commit f0a6e29 moved private methods from the provider into a module,
but in practice that couldn't be loaded. Instead, to silence rubocop
about class length, we'll keep the private methods, and tell it the
max length of a class is 200, because arbitrary numbers are arbitrary.
add upgrade recipe

Even though the newest (as of right now) release is set to install by
default, the attributes are set to 'upgrade' for splunk 4.3.7. This is
because internally, we use 4.2.1 and need to upgrade to 4.3.x before
we can upgrade to 6.0.1. Our internal splunk cookbook for 4.2.1 will
be used alongside this one until the upgrade is performed. This is
probably not a common use case, but the pattern is available for those
who want to reuse it. Simply set the appropriate attributes (see
`attributes/upgrade.rb`)
use dev mode for upgrade testing
add a spec for upgrade recipe
add upgrade notes to README
ensure upgrade recipe only run if attribute is enabled