r10k 1.3.5 → 1.4.0

data/.nodeset.yml

@@ -1,7 +0,0 @@
----
-default_set: 'centos-59-x64'
-sets:
-  'centos-59-x64':
-    nodes:
-      "main":
-        prefab: 'centos-59-x64'

data/.rspec

@@ -1 +0,0 @@
---default_path spec/unit

data/README.markdown

@@ -1,276 +0,0 @@
-r10k
-====
-
-Puppet environment and module deployment
-
-[![Build Status](https://travis-ci.org/adrienthebo/r10k.png?branch=master)](https://travis-ci.org/adrienthebo/r10k)
-
-Description
------------
-
-[librarian-puppet]: https://github.com/rodjek/librarian-puppet
-[workflow]: http://puppetlabs.com/blog/git-workflow-and-puppet-environments/
-
-r10k provides a general purpose toolset for deploying Puppet environments and
-modules. It implements the [Puppetfile][librarian-puppet] format and provides a native
-implementation of Puppet [dynamic environments][workflow].
-
-Installation
-------------
-
-r10k supports the following Ruby versions:
-
-  - 1.8.7 (POSIX minimum version)
-  - 1.9.3 (Windows minimum version)
-  - 2.0.0
-  - 2.1.0
-
-### Rubygems
-
-For general use, you should install r10k from Ruby gems:
-
-    gem install r10k
-    r10k help
-
-### Bundler
-
-If you have more specific needs or plan on modifying r10k you can run it out of
-a git repository using Bundler for dependencies:
-
-    git clone git://github.com/adrienthebo/r10k
-    cd r10k
-    bundle install
-    bundle exec r10k help
-
-### Puppet Enterprise
-
-Puppet Enterprise uses its own Ruby, so you need to use the correct version of gem when installing r10k.
-
-    /opt/puppet/bin/gem install r10k
-    r10k help
-
-Common Commands
----------------
-
-### Deploy all environments and Puppetfile specified modules
-
-    r10k deploy environment -p
-
-### Deploy all environments but don't update/install modules
-
-    r10k deploy environment
-
-### Deploy a specific environment, and its Puppetfile specified modules
-
-    r10k deploy environment your_env -p
-
-### Deploy a specific environment, but not its modules
-
-    r10k deploy environment your_env
-
-### Display all environments being managed by r10k
-
-    r10k deploy display
-
-### Display all environments being managed by r10k, and their modules.
-
-    r10k deploy display -p
-
-Puppetfile support
-------------------
-
-r10k can operate on a Puppetfile using the same syntax as librarian-puppet uses.
-Puppetfiles are a simple Ruby based DSL that specifies a list of modules to
-install, what version to install, and where to fetch them from. Unlike
-librarian-puppet dependency resolution is not yet implemented but is on the
-roadmap.
-
-Puppetfile based commands are under the `r10k puppetfile` subcommand.
-
-### Installing modules from git
-
-Puppet modules can be installed from any valid git repository:
-
-    mod 'rsyslog', :git => 'git://github.com/puppetlabs-operations/puppet-rsyslog.git'
-
-You can deploy a module from a specific branch, tag, or git ref. By default r10k
-will track `master` and will assume that you want to keep the module up to date.
-If you want to track a specific branch, then
-
-Examples:
-
-    # track master
-    mod 'filemapper',
-      :git => 'git://github.com/adrienthebo/puppet-filemapper.git'
-
-    # Install the filemapper module and track the 1.1.x branch
-    mod 'filemapper',
-      :git => 'git://github.com/adrienthebo/puppet-filemapper.git',
-      :ref => '1.1.x'
-
-    # Install filemapper and use the 1.1.1 tag
-    mod 'filemapper',
-      :git => 'git://github.com/adrienthebo/puppet-filemapper.git',
-      :ref => '1.1.1'
-
-    # Install filemapper and use a specific git commit
-    mod 'filemapper',
-      :git => 'git://github.com/adrienthebo/puppet-filemapper.git',
-      :ref => 'ec2a06d287f744e324cca4e4c8dd65c38bc996e2'
-
-### Installing modules from the Puppet forge
-
-Puppet modules can be installed from the forge using the Puppet module tool.
-
-    # This is currently a noop but will be supported in the future.
-    forge 'forge.puppetlabs.com'
-
-    # Install puppetlabs-stdlib from the Forge
-    mod 'puppetlabs/stdlib', '2.5.1'
-
-Basic Environment Structure
----------------------------
-
-r10k supports Dynamic Environments (see below), but simple environment structures
-are also supported.
-
-The basic structure of an environment that uses a Puppetfile to install modules is
-
-    .
-    |-- manifests
-      |-- site.pp
-    |-- Puppetfile
-    |-- .gitignore
-
-site.pp would contain your node definitions, and the Puppetfile would specify the modules
-to be installed.  r10k automatically creates the 'modules' directory when it applies the
-Puppetfile.
-
-It's important to put the modules directory in .gitignore so that git doesn't accidentally
-put it into the repo.
-
-    modules/
-
-Dynamic environment support
----------------------------
-
-r10k implements the dynamic environment workflow. Given a git repository with
-multiple branches r10k can create an environment for each branch. This means
-that you can use git with the normal branch-develop-merge workflow, and easily
-test your changes as you work.
-
-Deployment commands are implemented under the `r10k deploy` subcommand.
-
-### Git repository layout
-
-[modulepath]: http://docs.puppetlabs.com/references/stable/configuration.html#modulepath
-
-r10k makes the assumption that Puppet modules are stored in subdirectories of
-the Git repository. These directories are all loaded into the Puppet master with
-the [modulepath][modulepath] directive.
-
-For example, your Git repository would have a structure something like this:
-
-    .
-    ├── Puppetfile   # An optional Puppetfile
-    ├── dist         # Internally developed generic modules
-    └── site         # Modules for deploying custom services
-
-### Puppet master configuration
-
-In order to use dynamic environments, your Puppet masters will need to be
-configured to load manifests and modules relative to the requested environment:
-
-    [master]
-        modulepath = /etc/puppet/environments/$environment/modules:/etc/puppet/environments/$environment/dist
-
-        # If you use a top level manifest dir
-        manifestdir = /etc/puppet/environments/$environment/manifests
-        # If you use a specific site wide manifest
-        manifest = /etc/puppet/environments/$environment/manifests/nodes.pp
-
-Note that these settings go into the `[master]` section; you don't need to
-explicitly configure an environment section for each environment you want to
-use. (But you can if you want.)
-
-### Using dynamic environments with a Puppetfile
-
-
-r10k can implement a hybrid workflow with dynamic environments and Puppetfiles.
-If a Puppetfile is available at the root of a deployed environment, r10k can
-create and manage the `modules` directory within your Git repository.
-
-It's recommended that you add `/modules` to your project .gitignore.
-
-A deployed environment with a Puppetfile will look something like this:
-
-    .
-    ├── Puppetfile   # An optional Puppetfile
-    ├── dist         # Internally developed generic modules
-    ├── modules      # Puppet modules deployed by r10k
-    └── site         # Modules for deploying custom services
-
-It is also possible to set an alternate name/location for your `Puppetfile` and
-`modules` directory. This is useful if you want to control multiple environments
-and have a single location for your `Puppetfile`.
-
-Example:
-
-    PUPPETFILE=/etc/r10k.d/Puppetfile.production \
-    PUPPETFILE_DIR=/etc/puppet/modules/production \
-    /usr/bin/r10k puppetfile install
-
-### Dynamic environment configuration
-
-r10k uses a yaml based configuration file when handling deployments. The default
-location is in /etc/r10k.yaml and can be specified on the command line.
-
-### Example
-
-    # The location to use for storing cached Git repos
-    :cachedir: '/var/cache/r10k'
-
-    # A list of git repositories to create
-    :sources:
-      # This will clone the git repository and instantiate an environment per
-      # branch in /etc/puppet/environments
-      :plops:
-        remote: 'git@github.com:my-org/org-shared-modules'
-        basedir: '/etc/puppet/environments'
-
-Multiple git repositories can be specified, which is handy if environments are broken up by application.
-Application 1 could have its own environment repository with app1_dev, app1_tst, and app1_prd branches while
-Application 2 could have its own environment repository with app2_dev, app2_tst, app2_prd branches.
-
-You might want to take this approach if your environments vary greatly.  If you often find yourself making
-changes to your Application 1 environments that don't belong in your Application 2 environments, merging changes
-can become difficult if all of your environment branches are in a single repository.
-
-This approach also makes security easier as teams can be given access to control their application's environments
-without being able to accidentally impact other groups.
-
-### Multiple Environment Repositories Example
-
-    # The location to use for storing cached Git repos
-    :cachedir: '/var/cache/r10k'
-
-    # A list of git repositories to create
-    :sources:
-      # This will clone the git repository and instantiate an environment per
-      # branch in /etc/puppet/environments
-      :app1:
-        remote: 'git@github.com:my-org/app1-environments'
-        basedir: '/etc/puppet/environments'
-      :app2:
-        remote: 'git@github.com:my-org/app2-environments'
-        basedir: '/etc/puppet/environments'
-
-More information
-----------------
-
-The original impetus for r10k is explained at http://somethingsinistral.net/blog/rethinking-puppet-deployment/
-
-Contributors
-------------
-
-Please see the CHANGELOG for a listing of the (very awesome) contributors.

data/Rakefile

@@ -1 +0,0 @@
-require 'rspec-system/rake_task'

data/doc/puppetfile.markdown

@@ -1,87 +0,0 @@
-Puppetfile
-==========
-
-The Puppetfile is a way to reuse independent Puppet modules in your codebase.
-
-When directly working with Puppetfiles, you can use the `r10k puppetfile`
-subcommand to interact with a Puppetfile.
-
-When using r10k's deploy functionality, interacting with Puppetfiles is handled
-on a case by case basis.
-
-The Puppetfile format is actually implemented using a Ruby DSL so any valid Ruby
-expression can be used. That being said, being a bit too creative in the DSL
-can lead to surprising (read: bad) things happening, so consider keeping it
-simple.
-
-Module types
-------------
-
-### Git
-
-Modules can be installed via git.
-
-#### Examples
-
-    # Install puppetlabs/apache and keep it up to date with 'master'
-    mod 'apache',
-      :git => 'https://github.com/puppetlabs/puppetlabs-apache'
-
-    # Install puppetlabs/apache and track the 'docs_experiment' branch
-    mod 'apache',
-      :git => 'https://github.com/puppetlabs/puppetlabs-apache',
-      :ref => 'docs_experiment'
-
-You can also use the exact object type you want to check out. This may be a
-little bit more work but it has the advantage that r10k make certain
-optimizations based on the object type that you specify.
-
-    mod 'apache',
-      :git => 'https://github.com/puppetlabs/puppetlabs-apache',
-      :tag => '0.9.0'
-
-    mod 'apache',
-      :git    => 'https://github.com/puppetlabs/puppetlabs-apache',
-      :commit => '83401079053dca11d61945bd9beef9ecf7576cbf'
-
-You can also explicitly specify a branch, but this behaves the same as
-specifying :ref and is mainly useful for clarity.
-
-    mod 'apache',
-      :git    => 'https://github.com/puppetlabs/puppetlabs-apache',
-      :branch => 'docs_experiment'
-
-### Forge
-
-Modules can be installed using the Puppet module tool.
-
-If no version is specified the latest version available at the time will be
-installed, and will be kept at that version.
-
-    mod 'puppetlabs/apache'
-
-If a version is specified then that version will be installed.
-
-    mod 'puppetlabs/apache', '0.10.0'
-
-If the version is set to :latest then the module will be always updated to the
-latest version available.
-
-    mod 'puppetlabs/apache', :latest
-
-### SVN
-
-Modules can be installed via SVN.
-
-    mod 'apache',
-      :svn => 'https://github.com/puppetlabs/puppetlabs-apache/trunk'
-
-    mod 'apache',
-      :svn => 'https://github.com/puppetlabs/puppetlabs-apache/trunk',
-      :rev => '154'
-
-Alternately,
-
-    mod 'apache',
-      :svn      => 'https://github.com/puppetlabs/puppetlabs-apache/trunk',
-      :revision => '154'

data/spec/rspec-system-r10k/puppetfile.rb

@@ -1,24 +0,0 @@
-require 'tempfile'
-
-module RSpecSystem
-  module Puppetfile
-    def puppetfile_install(options = {})
-      expected_exit_code = options.fetch(:exit_code, 0)
-
-      shell %[r10k puppetfile install] do |results|
-        expect(results.exit_code).to eq expected_exit_code
-      end
-    end
-
-    def create_puppetfile(*mods)
-      tmp = Tempfile.new('rs-r10k-puppetfile')
-      tmp.write(mods.join("\n"))
-      tmp.flush
-      rcp :sp => tmp.path, :dp => "Puppetfile"
-    end
-  end
-end
-
-RSpec.configure do |config|
-  config.include RSpecSystem::Puppetfile
-end

data/spec/rspec-system-r10k/tmpdir.rb

@@ -1,32 +0,0 @@
-# Create and teardown a tmpdir around rspec example groups.
-
-module RSpecSystem
-  module Tmpdir
-    def tmpdir
-      dir = RSpec.configuration.tmpdir_stack.last
-      if dir.nil?
-        raise ArgumentError, "No tmpdir currently defined"
-      else
-        dir
-      end
-    end
-  end
-end
-
-RSpec.configure do |config|
-
-  config.add_setting(:tmpdir_stack, :default => [])
-
-  config.include RSpecSystem::Tmpdir
-  config.extend RSpecSystem::Tmpdir
-
-  config.before(:all, :rs_tmpdir => true) do |example|
-    shell 'mktemp -p $PWD -d rs.XXXXXXXX' do |sh|
-      RSpec.configuration.tmpdir_stack.push sh.stdout.chomp
-    end
-  end
-
-  config.after(:all, :rs_tmpdir => true) do |example|
-    RSpec.configuration.tmpdir_stack.pop
-  end
-end

data/spec/system-provisioning/el.rb

@@ -1,38 +0,0 @@
-module SystemProvisioning
-  module EL
-    def install_epel_release
-      rpm_install(
-        'epel-release',
-        'http://dl.fedoraproject.org/pub/epel/5/x86_64/epel-release-5-4.noarch.rpm'
-      )
-    end
-
-    def install_puppetlabs_release
-      rpm_install(
-        'puppetlabs-release',
-      'http://yum.puppetlabs.com/puppetlabs-release-el-5.noarch.rpm'
-      )
-    end
-
-    def yum_install(*pkgs)
-      pkgs = Array(*pkgs)
-
-      pkgs.each do |pkg|
-
-        check_cmd = shell "rpm -q --filesbypkg #{pkg}"
-        if check_cmd.exit_code != 0
-          shell "yum -y install #{pkg}"
-        end
-      end
-    end
-
-    def rpm_install(name, install_name = nil)
-      install_name ||= name
-
-      check_cmd = shell "rpm -q --filesbypkg #{name}"
-      if check_cmd.exit_code != 0
-        shell "rpm -Uvh #{install_name}"
-      end
-    end
-  end
-end