rump 0.2.1

data/LICENSE

@@ -0,0 +1,165 @@
+       GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions. 
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version. 
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

data/README.md

@@ -0,0 +1,118 @@
+Rump
+====
+
+Rump helps you run Puppet locally against a Git checkout.
+
+Rump encourages a Puppet workflow where you quickly + iteratively develop your
+Puppet manifests on a single machine, then push your changes up to a repository
+to deploy to the rest of your infrastructure.
+
+This workflow also complements a Capistrano or MCollective-style deployment,
+where you remotely instruct Rump to check out a copy of the latest manifests
+and run them.
+
+Rump also has the ability to freeze Puppet in to the manifests repository,
+letting you quickly test different versions of Puppet without waiting for
+packages to appear, and reducing the dependencies on a system to run Puppet
+down to just Ruby and git.
+
+Installing
+----------
+
+    $ gem install rump
+
+Using Rump
+----------
+
+Make sure you check out the [man pages](rump/blob/master/man/rump.1.ronn).
+
+Check out your repository of Puppet manifests:
+
+    $ rump clone git@github.com:me_at_example_dot_org/puppet.git
+
+You'll want to set up a `~/.gitconfig` in your home directory so you know who's
+making changes:
+
+    [user]
+    name = My Name
+    email = me@example.org
+
+    [push]
+    default = matching
+
+When you make changes, run Puppet through Rump:
+
+    $ sudo rump go
+
+You can append options you'd normally pass to the `puppet` command at the end
+of `rump go`:
+
+    $ sudo rump go --verbose --debug --noop
+
+There's nothing stopping you from running Rump against different checkouts/branches
+of manifests. This is especially powerful when developing locally with the following
+workflow:
+
+   1. `rump clone git@github.com:me_at_example_dot_org/puppet.git`
+   2. `rump go`
+   3. `cd puppet && git checkout -b new_feature`
+   4. Make your changes && `rump go --noop` to see what will change.
+   5. Apply the changes with `rump go`
+   6. *Iterate until everything's working*
+   7. `git checkout master && git merge new_feature`
+   8. `git push`
+
+Freezing Puppet
+---------------
+
+If you are using Git, you can freeze Puppet into your project as a submodule. This
+gives you a whole bunch of advantages:
+
+ * You only need Ruby installed on your system to run Puppet
+ * A checkout of your manifests also gives you Puppet
+ * Bind your manifests to a particular version of Puppet
+ * Test your manifests against new versions of Puppet in a separate branch
+ * Manage upgrades of Puppet outside your operating system's release cycle
+
+You can freeze Puppet very easily:
+
+    $ rump freeze
+
+This will freeze Puppet + Facter under `vendor/`. Alternatively, you can point
+the freezer at any Git repository (local or remote).
+
+When you run `rump go`, it checks whether you have frozen Puppet + Facter, and
+runs the frozen Puppet if available.
+
+You can also freeze in arbitrary Git repos:
+
+    $ rump freeze moonshine git://github.com/railsmachine/moonshine.git
+
+These will automatically be added to the load path when you run `rump go`
+
+Testing Rump
+------------
+
+There's a suite of Cucumber tests to fully exercise Rump in `features/`:
+
+    $ cucumber features/
+
+The scenarios are tagged with `@offline` and `@online`, depending on whether
+the test requires internet connectivity. Run all but `@online` tests with:
+
+    $ cucumber --tags ~@online features/
+
+Quirks
+------
+
+1. Puppet's fileserver (`source => "puppet:///..."` on File resources) doesn't
+   behave as expected on Puppet < 2.6. If you are using Puppet < 2.6, all files
+   need to be templates.
+
+2. Manifests need to be in modules so Puppet can pick them up correctly.
+
+License
+-------
+
+Copyright Rails Machine LLC 2010-2011, released under the LGPL. See
+[LICENSE](rump/blob/master/LICENSE) for more info.

data/Rakefile

@@ -0,0 +1,14 @@
+begin
+  require 'jeweler'
+  Jeweler::Tasks.new do |gemspec|
+    gemspec.name = "rump"
+    gemspec.summary = "Rump helps you run Puppet locally against a Git checkout."
+    gemspec.description = "Rump helps you run Puppet locally against a Git checkout. This is great for locally iterating your Puppet manifests very quickly, then pushng them up to a repository somewhere else to share the changes."
+    gemspec.email = "ops@railsmachine.com"
+    gemspec.homepage = "http://github.com/railsmachine/rump"
+    gemspec.authors = ["Lindsay Holmwood"]
+    gemspec.add_dependency 'thor', '0.13.4'
+  end
+rescue LoadError
+  puts "Jeweler not available. Install it with: gem install jeweler"
+end

data/VERSION

@@ -0,0 +1 @@
+0.2.1

data/bin/rump

@@ -0,0 +1,19 @@
+#!/usr/bin/env ruby
+
+begin
+  require 'rump'
+rescue LoadError
+  $: << File.expand_path(File.join(File.dirname(__FILE__), '..', 'lib'))
+  require 'rump'
+end
+
+if ARGV.any? {|arg| arg =~ /help|--help|-h/}
+  root = Pathname.new(File.dirname(__FILE__)).parent.expand_path
+  command = "man #{root + 'man' + 'rump.1'}"
+  exec(command)
+end
+
+command   = ARGV.first
+arguments = ARGV[1..-1]
+
+Rump.new.invoke(command, arguments)

data/features/rump.feature

@@ -0,0 +1,179 @@
+Feature: Rump
+  To iterate quickly
+  When writing and running
+  Puppet manifests
+  A user
+  Should have a helper tool
+  To smooth things out
+
+  @offline
+  Scenario: Cloning a repository
+    Given I am working in "/tmp"
+    And I have an empty git repository named "master-puppet"
+    And there is no "clone-puppet" repository
+    When I run "rump clone master-puppet clone-puppet"
+    Then I should have a git repository at "clone-puppet"
+
+  @offline
+  Scenario: Doing a puppet run
+    Given I am working in "/tmp"
+    And I have a simple Puppet repository named "foobar"
+    And there is no "simple-puppet" repository
+    And there is no "/tmp/checkout" file
+    And "puppet" is on my path
+    When I run "rump clone foobar simple-puppet"
+    Given I am working in "/tmp/simple-puppet"
+    When I run "rump go"
+    Then I should see a file at "/tmp/checkout"
+
+  @offline
+  Scenario: Initialising a safe repo
+    Given I am working in "/tmp"
+    And there is no "safe-puppet" repository
+    And there is no "/tmp/checkout" file
+    When I run "rump init safe-puppet"
+    Then I should have a git repository at "safe-puppet"
+
+  @offline
+  Scenario: Verifying author name
+    Given I am working in "/tmp"
+    And there is no "safe-puppet" repository
+    And there is no "/tmp/checkout" file
+    When I run "rump init safe-puppet"
+    Then I should have a git repository at "safe-puppet"
+    Given I am working in "/tmp/safe-puppet"
+    When I touch "/tmp/safe-puppet/random"
+    When I run "git add ."
+    Then running "GIT_AUTHOR_NAME=root git commit -m 'created random' ." should fail
+
+  @offline
+  Scenario: Verifying author email
+    Given I am working in "/tmp"
+    And there is no "safe-puppet" repository
+    And there is no "/tmp/checkout" file
+    When I run "rump init safe-puppet"
+    Then I should have a git repository at "safe-puppet"
+    Given I am working in "/tmp/safe-puppet"
+    When I touch "/tmp/safe-puppet/random"
+    When I run "git add ."
+    Then running "GIT_AUTHOR_EMAIL=me@$(hostname) git commit -m 'created random' ." should fail
+
+  @offline
+  Scenario: Setting author email
+    Given I am working in "/tmp"
+    And there is no "whoami-email-puppet" repository
+    And there is no "/tmp/checkout" file
+    When I run "rump init whoami-email-puppet"
+    Then I should have a git repository at "whoami-email-puppet"
+    Given I am working in "/tmp/whoami-email-puppet"
+    When I run "rump whoami 'Spoons McDoom <spoons@mcdoom.com>'"
+    When I touch "/tmp/whoami-email-puppet/random"
+    When I run "git add ."
+    Then running "GIT_AUTHOR_EMAIL=$(git config user.email) git commit -m 'created random' ." should succeed
+
+  @offline
+  Scenario: Setting author name
+    Given I am working in "/tmp"
+    And there is no "whoami-name-puppet" repository
+    And there is no "/tmp/checkout" file
+    When I run "rump init whoami-name-puppet"
+    Then I should have a git repository at "whoami-name-puppet"
+    Given I am working in "/tmp/whoami-name-puppet"
+    When I run "rump whoami 'Spoons McDoom <spoons@mcdoom.com>'"
+    When I touch "/tmp/whoami-name-puppet/random"
+    When I run "git add ."
+    Then running "GIT_AUTHOR_NAME=$(git config user.name) git commit -m 'created random' ." should succeed
+
+  @offline
+  Scenario: Getting author name and email
+    Given I am working in "/tmp"
+    And there is no "whoami-getter-puppet" repository
+    And there is no "/tmp/checkout" file
+    When I run "rump init whoami-getter-puppet"
+    Then I should have a git repository at "whoami-getter-puppet"
+    Given I am working in "/tmp/whoami-getter-puppet"
+    When I run "rump whoami 'Spoons McDoom <spoons@mcdoom.com>'"
+    Then running "rump whoami" should output "Spoons McDoom <spoons@mcdoom.com>"
+
+  @online
+  Scenario: Freezing Puppet + Facter as submodules
+    Given I am working in "/tmp"
+    And I have a simple Puppet repository named "foobar"
+    And there is no "simple-puppet" repository
+    And there is no "/tmp/checkout" file
+    When I run "rump clone foobar simple-puppet"
+    Given I am working in "/tmp/simple-puppet"
+    When I run "rump freeze"
+    And I run "rump go"
+    Then I should see a file at "/tmp/checkout"
+
+  @online
+  Scenario: Automatically initialising frozen submodules on clone
+    Given I am working in "/tmp"
+    And I have a simple Puppet repository named "foobar"
+    And there is no "simple-puppet" repository
+    And there is no "frozen-puppet" repository
+    When I run "rump clone foobar simple-puppet"
+    Given I am working in "/tmp/simple-puppet"
+    When I run "rump freeze"
+    And I run "git add ."
+    And I run "git commit -m 'frozen puppet + facter' ."
+    Given I am working in "/tmp"
+    When I run "rump clone simple-puppet frozen-puppet"
+    Then I should see a directory at "/tmp/frozen-puppet/vendor/facter"
+    Then I should see a directory at "/tmp/frozen-puppet/vendor/puppet"
+
+  @online
+  Scenario: Freezing a specific submodule
+    Given I am working in "/tmp"
+    And I have a simple Puppet repository named "foobar"
+    And there is no "simple-puppet" repository
+    And there is no "/tmp/checkout" file
+    When I run "rump clone foobar simple-puppet"
+    Given I am working in "/tmp/simple-puppet"
+    When I run "rump freeze facter git://github.com/puppetlabs/facter.git"
+    And I run "rump freeze puppet git://github.com/puppetlabs/puppet.git"
+    And I run "rump go"
+    Then I should see a file at "/tmp/checkout"
+
+  @online
+  Scenario: Freezing a specific submodule at a specific release
+    Given I am working in "/tmp"
+    And I have a simple Puppet repository named "foobar"
+    And there is no "tagged-puppet" repository
+    And there is no "/tmp/checkout" file
+    When I run "rump clone foobar tagged-puppet"
+    Given I am working in "/tmp/tagged-puppet"
+    When I run "rump freeze facter git://github.com/puppetlabs/facter.git --release=1.5.7"
+    And I run "rump freeze puppet git://github.com/puppetlabs/puppet.git --release=0.25.4"
+    And I run "rump go"
+    Then I should see a file at "/tmp/checkout"
+
+  @online
+  Scenario: Freezing and running Puppet 2.6
+    Given I am working in "/tmp"
+    And I have a simple Puppet 2.6 repository named "foobar"
+    And there is no "tagged-puppet" repository
+    And there is no "/tmp/checkout" file
+    When I run "rump clone foobar tagged-puppet"
+    Given I am working in "/tmp/tagged-puppet"
+    When I run "rump freeze facter git://github.com/puppetlabs/facter.git --release=1.5.8"
+    And I run "rump freeze puppet git://github.com/puppetlabs/puppet.git --release=2.6.4"
+    And I run "rump go"
+    Then I should see a file at "/tmp/checkout"
+
+  @offline
+  Scenario: Generating project scaffolding
+    Given I am working in "/tmp/"
+    When I run "rump scaffold my-new-project"
+    Given I am working in "/tmp/my-new-project"
+    Then I should see the following directories:
+      | directory                     |
+      | /tmp/my-new-project           |
+      | /tmp/my-new-project/manifests |
+      | /tmp/my-new-project/modules   |
+      | /tmp/my-new-project/vendor    |
+    And I should see a file at "/tmp/my-new-project/README"
+
+
+