- 01 Feb, 2015 2 commits
-
-
Stefan Schulte authored
-
Stefan Schulte authored
* duritong/autorequire: autorequire a local source
-
- 30 Jan, 2015 1 commit
-
-
mh authored
if the local key to import is also managed by puppet, this adds an automatic require dependency on that file.
-
- 27 Jan, 2015 3 commits
-
-
Stefan Schulte authored
-
Stefan Schulte authored
* mmoll-os_metadata: update OS data in metadata.json
-
Michael Moll authored
-
- 22 Jan, 2015 1 commit
-
-
Stefan Schulte authored
The license in metadata.json must be present in the SPDX License List (http://spdx.org/licenses) for puppetforge to detect the correct license. The name of the Apache license was misspelled in metadata.json, which had a negetive effect on Metadata Quality score. Also the metadata.json has to include to supported operating systems. While this module is probably supported on any system that uses RPM, I have only tested it on RHEL5 and RHEL6.
-
- 21 Jan, 2015 4 commits
-
-
Stefan Schulte authored
inside .travis.yml we worked with PUPPET_VERSION like ~> 3.0.0 which gives us the latest version inside the same major release. This did not work together with the Gemfile that is created with puppet module generate, because it expects fixed versions. Modify the Gemfile to allow the old behaviour again.
-
Stefan Schulte authored
ruby 1.9 and above was not really supported before puppet 3.x [1] so don't test any of these combinations. These combinations actually were excluded before, but the matrix got messed up in the previous commit. [1] https://docs.puppetlabs.com/guides/platforms.html#ruby-versions
-
Stefan Schulte authored
The environment variables inside Gemfile changed (adopted to puppet module generate) so we also have to modify the travis file to set the correct environment variables when testing against specific puppet/facter versions
-
Stefan Schulte authored
To be able to release the module puppet module generate was used to get a basic sketch of the Gemfile and metadata.json file. Also added a changelog as puppet forge modules are versioned.
-
- 06 Jan, 2015 3 commits
-
-
Stefan Schulte authored
-
Stefan Schulte authored
* genebean-readme-update: Added info on how to find the keyID to the readme file.
-
Gene Liverman authored
-
- 05 Jan, 2015 1 commit
-
-
Stefan Schulte authored
Running the specs with rspec3 leads to the following deprecation warning: Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead So switch to the new expect syntax
-
- 04 Apr, 2014 2 commits
-
-
Stefan Schulte authored
-
Stefan Schulte authored
Since the specs for the type do not use any provider features we do not have to create a fake provider.
-
- 23 Jun, 2013 1 commit
-
-
Stefan Schulte authored
PuppetLabs has released a seperate gem to make writing spec tests easier (puppetlabs_spec_helper). Using this gem makes a lot of files obsolete that were initially copied form the puppetlabs/puppet project.
-
- 26 Jun, 2012 3 commits
-
-
Stefan Schulte authored
If there is currently no key present in the RPM keyring rpm -q returns with a non-zero exitcode. This case is now handled properly so no error message is shown when running puppet.
-
Stefan Schulte authored
Because we never really execute rpm and are only testing the provider we are never asked suitable? so we can just drop a few stubs of FileTest
-
Stefan Schulte authored
The rpm_key type was renamed to rpmkey pretty early but the spec directories should also reflect the new name.
-
- 25 Jun, 2012 1 commit
-
-
Stefan Schulte authored
The new type can be used to describe an imported gpg key
-
- 24 Jun, 2012 1 commit
-
-
Stefan Schulte authored
Add README and copy the necessary testframework from the puppet codebase
-