Merge pull request #267 from voxpupuli/rnelson0-patch-1
Rnelson0 patch 1
Merge pull request #277 from dhoppe/remove_duplicate
Remove duplicate CONTRIBUTING.md file
Merge pull request #279 from voxpupuli/modulesync
modulesync 2.10.0
Merge pull request #283 from voxpupuli/modulesync
modulesync 2.12.0
Merge pull request #284 from voxpupuli/rewrite-acceptance-tests
Use voxpupuli-acceptance
Add possibility to stop recursion on gnupghome (#290)
* Add possibility to stop recursion on gnupghome * Fix README.md to pass travis check. * Fix more layout regarded as errors * Fix more layout regarded as errors * Fix more layout regarded as errors * Fix more layout regarded as errors * Fix more layout regarded as errors * Fix more layout regarded as errors * I stand corrected. It works now. I mustve done something special on my part. * Specify boolean datatype for eyaml_gpg_gnupghome_recurse parameter. * Add test for eyaml_gpg and some other minor checks I found some checks missing from rake runs, and fixed them. Doing this I mangled hiera_spec.rb to achieve consistent naming of keysdir. When I started I used default and that caused 3 different namings of the same directory. That seems silly. The reason it ended up being /dev/null/keys is that theam YAML eyaml loader sets confdir to "/dev/null" The string "/dev/null" is not mentioned anywhere in the code. So I went with it and changed keysdir to /dev/null/keys instead of /etc/keys. This is a small change, that increases the coverage percentage when I check some file in the eyaml_gpg_spec.rb. Also added a check for the deep_merge class, just becasue it was easy and on my way. I am getting the hang of this now - but if you would ask me what I have done and how, I would have to do answer in a Mr. Miagi-style. Don't know. Firsta time. * Changing layout to meet strict requirements. This is kindoff a guessing game. * Changing layout to meet strict requirements. This is kindoff a guessing game. * Changing layout to meet strict requirements. This is kindoff a guessing game. * Changing layout to meet strict requirements. This is kindoff a guessing game. * Set Key-Usage to encrypt Only let key be used for (de)encryption. A key without passphrase shouldn't sign anything or be used to authenticate anything. You can trust it to decrypt messages destined to be decrypted by it, but you can never trust anything that is signed by it. * Revert "Set Key-Usage to encrypt" My bad, this has nothing to do in this pull request. This reverts commit 1871e63.
Merge pull request #286 from voxpupuli/modulesync
modulesync 3.1.0 & puppet-lint updates
Merge pull request #291 from bastelfreak/linter
puppet-lint: autofix