(maint) add puppetise laptop (puppetlabs#36)

* updated install script to create custom fact

* updated site to use new qa modules

* adding new qa modules

* update to source xcode file correctly

* updated $path for running xcode script

* added gemset and bundler

* adding floaty gem

* adding software module

* update to use seamymckenna fork of bitbar

* update to use root to config def rvm gemset

* update to not use root to config def rvm gemset

tools/laptop_puppetisation/README.md

@@ -1,17 +1,15 @@
-Manifest to Install homebrew (with git, tmux & gnupg), rvm, ruby (2.0.0, 2.2.0, 2.3.0), Bundler & Rake for each Ruby Version
+Create a manifest on an agent to test the modules as part of the QA Puppetise Laptop Project
 
 Also includes a ruby file 'install_agent.rb' which does the following:
 - Creates User 'wilson' with password 'password' and Home Directory
 - Reboots Agent
 - Installs puppet agent (Latest)
-- Install module dependencies of manifest:
-- - maestrodev-rvm
-- - gildas-homebrew
+- Install modules from modules folder:
 - Copies site.pp (manifest) to /etc/puppetlabs/code/environments/production/manifests/site.pp agent
 
 How-To Use
 beaker-hostgenerator osx1011-64 > macosx.yml
 beaker --preserve --provision --hosts macosx.yml --pre-suite install_agent.rb --log-level debug
 
 After this, you can login as root and apply the manifest
-Once manifest is applied, login as wilson:password and rvm etc. will be available to you
+Once manifest is applied, login as wilson:password and rvm etc. will be available to you

tools/laptop_puppetisation/install_agent.rb

@@ -12,20 +12,34 @@
 chown wilson /Users/wilson
 CREATE_USER
 
-module_dependencies = ['maestrodev-rvm', 'gildas-homebrew', 'puppetlabs-vcsrepo']
+create_custom_facts = <<CREATE_CUSTOM_FACTS
+mkdir /Users/wilson/custom_facts &&
+echo "export FACTERLIB='/Users/wilson/custom_facts/'" > /var/root/.profile &&
+export FACTERLIB=/Users/wilson/custom_facts/ &&
+echo "require 'facter'" > /Users/wilson/custom_facts/mac_current_user.rb &&
+echo "Facter.add('mac_current_user') do" >> /Users/wilson/custom_facts/mac_current_user.rb &&
+echo "  setcode do" >> /Users/wilson/custom_facts/mac_current_user.rb  &&
+echo "    'wilson'" >> /Users/wilson/custom_facts/mac_current_user.rb &&
+echo "  end" >> /Users/wilson/custom_facts/mac_current_user.rb  &&
+echo "end" >> /Users/wilson/custom_facts/mac_current_user.rb
+CREATE_CUSTOM_FACTS
+
+module_dependencies = ['homebrew','gnupg','qahomebrew','qapackages','qarubyecosystem','qavmpoolerbitbar','qaxcode','rvm','stdlib','vcsrepo', 'software', 'vmfloaty']
 
 test_name "Create user wilson & Installing Puppet Agent" do
   agents.each{ |agent|
     #Add user wilson:password, then reboot
     on agent, create_user_script
+    on agent, create_custom_facts
     agent.reboot
-
-    #Install agent and dependent modules
     install_puppet_agent_on agent
+
     module_dependencies.each do |module_name|
-      on agent, "puppet module install #{module_name}"
+      copy_module_to(agent, :source => "./modules/#{module_name}",
+			    :target_module_path => "/etc/puppetlabs/code/environments/production/modules/",
+                            :module_name => "#{module_name}")
+      #on agent, "puppet module install #{module_name}"
     end
-
     scp_to(agent, 'site.pp', '/etc/puppetlabs/code/environments/production/manifests/site.pp')
   } 
 end

tools/laptop_puppetisation/modules/gnupg/CHANGELOG

@@ -0,0 +1,49 @@
+2016-01-22 - Dejan Golja <[email protected]> - 1.2.3
+* Another retry to rebuild repack the module to fix the PaxHeaders bsd tar bug
+
+2016-01-18 - Dejan Golja <[email protected]> - 1.2.2
+* module Remove PaxHeaders from distributed package, so it works with r10k
+
+2015-07-04 - Dejan Golja <[email protected]> - 1.2.1
+* remove (present|absent) restriction on $package_ensure
+* add support for SLES
+
+2015-05-16 - Dejan Golja <[email protected]> - 1.2.0
+* autorequire user type when using gnupg_key (tnx to [email protected])
+* added two new custom facts:
+  * gnupg_command - get full path to gpg exe
+  * gnupg_installed - determine if gpg exe exists on system
+
+2015-03-24 - Dejan Golja <[email protected]> - 1.1.1
+* supports username with -
+
+2015-02-21 - Dejan Golja <[email protected]> - 1.1.0
+* properly supports private key (added new paramater key_type
+  for gnupg_key type)
+* added new parameter key_content for gnupg_key type
+  to make it easier integrate hiera lookups. More info check README
+
+Special thanks to Tobias Clemson (https://github.com/tobyclemson)
+
+2014-10-20 - Dejan Golja <[email protected]> - 1.0.0
+* remove support for puppet 2.7.x due to the native type
+* added beaker system spec tests
+* Update type definition so it uses Puppet::Util::Execution.execute
+  instead of Puppet::Util::SUIDManager.run_and_capture (deprecated)
+* bump version to 1.0.0
+
+2014-10-07 - Dejan Golja <[email protected]> - 0.0.5
+* bugfix for https keys
+
+2014-08-17 - Dejan Golja <[email protected]> - 0.0.4
+* Update metadata.json and removed Modulefile due to 
+  as of Puppet 3.6 the Modulefile has been deprecated
+
+2014-03-16 - Dejan Golja <[email protected]> - 0.0.3
+* Added Puppet Forge Search by Module Compatibility
+
+2013-10-22 - Dejan Golja <[email protected]> - 0.0.2
+* public release for Forge
+
+2013-10-12 - Dejan Golja <[email protected]> - 0.0.1
+* initial beta version not released to the public

tools/laptop_puppetisation/modules/gnupg/CONTRIBUTING.md

@@ -0,0 +1,216 @@
+Checklist (and a short version for the impatient)
+=================================================
+
+  * Commits:
+
+    - Make commits of logical units.
+
+    - Check for unnecessary whitespace with "git diff --check" before
+      committing.
+
+    - Commit using Unix line endings (check the settings around "crlf" in
+      git-config(1)).
+
+    - Do not check in commented out code or unneeded files.
+
+    - The first line of the commit message should be a short
+      description (50 characters is the soft limit, excluding ticket
+      number(s)), and should skip the full stop.
+
+    - Associate the issue in the message. The first line should include
+      the issue number in the form "(#XXXX) Rest of message".
+
+    - The body should provide a meaningful commit message, which:
+
+      - uses the imperative, present tense: "change", not "changed" or
+        "changes".
+
+      - includes motivation for the change, and contrasts its
+        implementation with the previous behavior.
+
+    - Make sure that you have tests for the bug you are fixing, or
+      feature you are adding.
+
+    - Make sure the test suites passes after your commit:
+      `bundle exec rspec spec/acceptance` More information on [testing](#Testing) below
+
+    - When introducing a new feature, make sure it is properly
+      documented in the README.md
+
+  * Submission:
+
+    * Preferred method:
+
+      - Fork the repository on GitHub.
+
+      - Push your changes to a topic branch in your fork of the
+        repository. (the format ticket/1234-short_description_of_change is
+        usually preferred for this project).
+
+      - Submit a pull request to the repository in the puppetlabs
+        organization.
+
+The long version
+================
+
+  1.  Make separate commits for logically separate changes.
+
+      Please break your commits down into logically consistent units
+      which include new or changed tests relevant to the rest of the
+      change.  The goal of doing this is to make the diff easier to
+      read for whoever is reviewing your code.  In general, the easier
+      your diff is to read, the more likely someone will be happy to
+      review it and get it into the code base.
+
+      If you are going to refactor a piece of code, please do so as a
+      separate commit from your feature or bug fix changes.
+
+      We also really appreciate changes that include tests to make
+      sure the bug is not re-introduced, and that the feature is not
+      accidentally broken.
+
+      Describe the technical detail of the change(s).  If your
+      description starts to get too long, that is a good sign that you
+      probably need to split up your commit into more finely grained
+      pieces.
+
+      Commits which plainly describe the things which help
+      reviewers check the patch and future developers understand the
+      code are much more likely to be merged in with a minimum of
+      bike-shedding or requested changes.  Ideally, the commit message
+      would include information, and be in a form suitable for
+      inclusion in the release notes for the version of Puppet that
+      includes them.
+
+      Please also check that you are not introducing any trailing
+      whitespace or other "whitespace errors".  You can do this by
+      running "git diff --check" on your changes before you commit.
+
+  2.  Sending your patches
+
+      To submit your changes via a GitHub pull request, we _highly_
+      recommend that you have them on a topic branch, instead of
+      directly on "master".
+      It makes things much easier to keep track of, especially if
+      you decide to work on another thing before your first change
+      is merged in.
+
+      GitHub has some pretty good
+      [general documentation](http://help.github.com/) on using
+      their site.  They also have documentation on
+      [creating pull requests](http://help.github.com/send-pull-requests/).
+
+      In general, after pushing your topic branch up to your
+      repository on GitHub, you can switch to the branch in the
+      GitHub UI and click "Pull Request" towards the top of the page
+      in order to open a pull request.
+
+
+  3.  Update the related GitHub issue.
+
+      If there is a GitHub issue associated with the change you
+      submitted, then you should update the ticket to include the
+      location of your branch, along with any other commentary you
+      may wish to make.
+
+Testing
+=======
+
+Getting Started
+---------------
+
+This puppet modules provide [`Gemfile`](./Gemfile)s which can tell a ruby
+package manager such as [bundler](http://bundler.io/) what Ruby packages,
+or Gems, are required to build, develop, and test this software.
+
+Please make sure you have [bundler installed](http://bundler.io/#getting-started)
+on your system, then use it to install all dependencies needed for this project,
+by running
+
+```shell
+% bundle install
+Fetching gem metadata from https://rubygems.org/........
+Fetching gem metadata from https://rubygems.org/..
+Using rake (10.1.0)
+Using builder (3.2.2)
+-- 8><-- many more --><8 --
+Using rspec-system-puppet (2.2.0)
+Using serverspec (0.6.3)
+Using rspec-system-serverspec (1.0.0)
+Using bundler (1.3.5)
+Your bundle is complete!
+Use `bundle show [gemname]` to see where a bundled gem is installed.
+```
+
+NOTE some systems may require you to run this command with sudo.
+
+If you already have those gems installed, make sure they are up-to-date:
+
+```shell
+% bundle update
+```
+
+With all dependencies in place and up-to-date we can now run the tests:
+
+```shell
+% rake spec
+```
+
+This will execute all the [rspec tests](http://rspec-puppet.com/) tests
+under [spec/defines](./spec/defines), [spec/classes](./spec/classes),
+and so on. rspec tests may have the same kind of dependencies as the
+module they are testing. While the module defines in its [Modulefile](./Modulefile),
+rspec tests define them in [.fixtures.yml](./fixtures.yml).
+
+Some puppet modules also come with [beaker](https://github.com/puppetlabs/beaker)
+tests. These tests spin up a virtual machine under
+[VirtualBox](https://www.virtualbox.org/)) with, controlling it with
+[Vagrant](http://www.vagrantup.com/) to actually simulate scripted test
+scenarios. In order to run these, you will need both of those tools
+installed on your system.
+
+You can run them by issuing the following command
+
+```shell
+% rake spec_clean
+% rspec spec/acceptance
+```
+
+This will now download a pre-fabricated image configured in the [default node-set](./spec/acceptance/nodesets/default.yml),
+install puppet, copy this module and install its dependencies per [spec/spec_helper_acceptance.rb](./spec/spec_helper_acceptance.rb)
+and then run all the tests under [spec/acceptance](./spec/acceptance).
+
+Writing Tests
+-------------
+
+XXX getting started writing tests.
+
+If you have commit access to the repository
+===========================================
+
+Even if you have commit access to the repository, you will still need to
+go through the process above, and have someone else review and merge
+in your changes.  The rule is that all changes must be reviewed by a
+developer on the project (that did not write the code) to ensure that
+all changes go through a code review process.
+
+Having someone other than the author of the topic branch recorded as
+performing the merge is the record that they performed the code
+review.
+
+
+Additional Resources
+====================
+
+* [Getting additional help](http://projects.puppetlabs.com/projects/puppet/wiki/Getting_Help)
+
+* [Writing tests](http://projects.puppetlabs.com/projects/puppet/wiki/Development_Writing_Tests)
+
+* [Patchwork](https://patchwork.puppetlabs.com)
+
+* [Contributor License Agreement](https://projects.puppetlabs.com/contributor_licenses/sign)
+
+* [General GitHub documentation](http://help.github.com/)
+
+* [GitHub pull request documentation](http://help.github.com/send-pull-requests/)
+

tools/laptop_puppetisation/modules/gnupg/Gemfile

@@ -0,0 +1,33 @@
+source ENV['GEM_SOURCE'] || "https://rubygems.org"
+
+group :development, :test do
+  gem 'rake',                   :require => false
+  gem 'rspec-core','~> 3.1.7',  :require => false
+  gem 'rspec-puppet',           :require => false
+  gem 'puppetlabs_spec_helper', :require => false
+  gem 'puppet-lint',            :require => false
+  gem 'puppet_facts',           :require => false
+  gem 'json',                   :require => false
+  gem 'metadata-json-lint',     :require => false
+end
+
+group :system_tests do
+  gem 'beaker', '~> 2.4',    :require => false
+  gem 'beaker-rspec',        :require => false
+  gem 'serverspec',          :require => false
+  gem 'rspec-system-puppet', :require => false
+end
+
+if facterversion = ENV['FACTER_GEM_VERSION']
+  gem 'facter', facterversion, :require => false
+else
+  gem 'facter', :require => false
+end
+
+if puppetversion = ENV['PUPPET_GEM_VERSION']
+  gem 'puppet', puppetversion, :require => false
+else
+  gem 'puppet', :require => false
+end
+
+# vim:ft=ruby