initial fork

Author: Dave Try

CHANGELOG.md

@@ -0,0 +1,102 @@
+##2016-07-13 - Version 5.3
+
+Several minor improvements to the Docker Compose support including:
+
+* Support for v2 of the Compose file syntax
+* Support refreshing the docker_compose resource
+* The ability to pass an install_path for custom installations
+* Passing arguments to docker-compose up
+* Ensuring curl is available when using it to install Compose
+
+New parameters for docker::run including stop_wait_time to allow
+containers time to stop when killed
+
+New parameters for the docker class, including icc, storage_setup_file
+
+Support for the overlay2 storage driver and the splunk log driver.
+
+Improvements to management when not using the upstream repository,
+including doing less to manage potentially unneeded dependencies.
+
+Support multiple registry authentications on the same host.
+
+Fix an issue with using docker::run on Swarm.
+
+Fix a number of issues if running the module with strict variables
+enabled, and add this to the tested conbinations.
+
+
+##2016-03-30 - Version 5.2
+
+This release includes some minor features and several bug fixes,
+including:
+
+* Support for specifying TLS settings for Docker connectivity
+* Added support for BIP and MTU options
+* Ensure containers are restarted if Docker is restarted
+* Support creating Docker Networks using Hiera
+* Fix issues with left over containers when using
+  remove_container_on_stop
+* Use the plain HTTP package repository rather than HTTPS
+* Added Gentoo support
+* Support managing labels on Docker Engine
+
+
+##2016-02-12 - Version 5.1
+
+Note that changes in Docker 1.10 changed the flag used to start the
+docker daemon. If you are using a version of docker prior to 1.8 you
+will need to pass the docker_subcommand parameter with the '-d' option.
+
+
+This release includes a few minor bug-fixes along with several new features:
+
+* The module now allows for installing, and running, Docker Compose from
+  Puppet, using both the docker::compose class the the docker_compose
+  type.
+* The module also now allows for the creation and management of Docker
+  Network using the new docker_network type
+* And the docker::run type now supports ensure => absent
+* Lots of options to configure the docker deaemon network
+* Support for installing Docker CS, the commercially supported Docker
+  engine
+* Disable managing the docker service in Puppet
+
+Fixes include:
+
+* Ensuring idempotence of docker::run using deprecated params
+* Properly escaping variables in unless for docker::exec
+* Explicitly specify systemd as the service provider for recent versions
+  of Ubuntu and Debian
+* Fix issue with Amazon Linux support
+
+##2015-12-18 - Version 5.0
+
+Note that this is a major release and in particular changes the default
+repository behaviour so all supported operating systems use the new
+Docker upstream repos.
+
+This release includes:
+
+* Full docker label support
+* Support for CentOS 7 repository options
+* Support for Docker's built-in restart policy
+* Docker storage setup options support for systemd
+* The ability to configure log drivers
+* Support unless for docker exec
+* Full datamapper property support, and deprecation of old property
+  names
+* Allow arbitrary parameters to be passed to systemd
+* Add ZFS storage driver support
+* Allow docker image resources to be refreshed, pulling the latest
+* Deprecates use_name, all containers are now named for the resource
+* Support for Puppet 4.3 with the stricter parser
+
+
+As well as fixes for:
+
+* Fix running=false to not start the docker image on docker restart
+  under systemd
+* Prevent timeouts for docker run
+* Ensure docker is running before attempting to use docker run
+* Obsfucate registry password from Puppet logs

CONTRIBUTING.md

@@ -0,0 +1,84 @@
+This module has grown over time based on a range of contributions from
+people using it. If you follow these contributing guidelines your patch
+will likely make it into a release a little quicker.
+
+
+## Contributing
+
+1. Fork the repo.
+
+2. Run the tests. We only take pull requests with passing tests, and
+   it's great to know that you have a clean slate
+
+3. Add a test for your change. Only refactoring and documentation
+   changes require no new tests. If you are adding functionality
+   or fixing a bug, please add a test.
+
+4. Make the test pass.
+
+5. Push to your fork and submit a pull request.
+
+
+## Dependencies
+
+The testing and development tools have a bunch of dependencies,
+all managed by [bundler](http://bundler.io/) according to the
+[Puppet support matrix](http://docs.puppetlabs.com/guides/platforms.html#ruby-versions).
+By default the tests use a baseline version of Puppet.
+
+If you have Ruby 2.x or want a specific version of Puppet,
+you must set an environment variable such as:
+
+    export PUPPET_GEM_VERSION="~> 3.2.0"
+
+Install the dependencies like so...
+
+    bundle install
+
+...or promote reuse of bundled gems across projects by running:
+
+    bundle install --path=~/.bundle
+
+## Syntax and style
+
+The test suite will run [Puppet Lint](http://puppet-lint.com/) and
+[Puppet Syntax](https://github.com/gds-operations/puppet-syntax) to
+check various syntax and style things. You can run these locally with:
+
+    bundle exec rake lint
+    bundle exec rake syntax
+
+## Running the unit tests
+
+The unit test suite covers most of the code, as mentioned above please
+add tests if you're adding new functionality. If you've not used
+[rspec-puppet](http://rspec-puppet.com/) before then feel free to ask
+about how best to test your new feature. Running the test suite is done
+with:
+
+    bundle exec rake spec
+
+Note also you can run the syntax, style and unit tests in one go with:
+
+    bundle exec rake test
+
+## Integration tests
+
+The unit tests just check the code runs, not that it does exactly what
+we want on a real machine. For that we're using
+[Beaker](https://github.com/puppetlabs/beaker).
+This fires up a new virtual machine (using vagrant) and runs a series of
+simple tests against it after applying the module. You can run this
+with:
+
+    bundle exec rake beaker
+
+This will run the tests on an Ubuntu 12.04 virtual machine. You can also
+run the integration tests against Centos 6.5 with:
+
+    BEAKER_set=centos-70-x64 bundle exec rake beaker
+
+Or with Ubuntu 14.04 with:
+
+    BEAKER_set=ubuntu-1404-x64 bundle exec rake beaker
+

Gemfile

@@ -0,0 +1,40 @@
+source "https://rubygems.org"
+
+group :test do
+  gem "rake", "~> 10.0"
+  if puppet_gem_version = ENV['PUPPET_GEM_VERSION']
+    gem "puppet", puppet_gem_version
+  elsif puppet_git_url = ENV['PUPPET_GIT_URL']
+    gem "puppet", :git => puppet_git_url
+  else
+    gem "puppet"
+  end
+  gem "puppet-lint"
+  gem "puppet-lint-unquoted_string-check"
+  gem "rspec-puppet"
+  gem "puppet-syntax"
+  gem "puppetlabs_spec_helper"
+  gem "metadata-json-lint", "1.1.0"
+  gem "rspec"
+  gem "rspec-retry"
+  gem "simplecov", ">= 0.11.0"
+  gem "simplecov-console"
+  gem "json_pure", "<= 2.0.1" # 2.0.2 requires Ruby 2+
+end
+
+group :system_tests do
+  gem "beaker-puppet_install_helper", :require => false
+  gem "beaker-rspec"
+  gem "beaker", "~> 2.0"
+end
+
+group :development do
+  gem "travis"
+  gem "travis-lint"
+  gem "puppet-blacksmith"
+  gem "guard-rake"
+  gem "pry"
+  gem "yard"
+  gem 'parallel_tests' # requires at least Ruby 1.9.3
+  gem 'rubocop', :require => false # requires at least Ruby 1.9.2
+end

Guardfile

@@ -0,0 +1,17 @@
+notification :off
+
+scope group: :spec
+
+group :spec do
+  guard :rake, :task => 'test' do
+    watch(%r{^lib\/.+\.rb$})
+    watch(%r{^spec\/.+\.rb$})
+		watch(%r{^manifests\/.+\.pp$})
+  end
+end
+
+group :acceptance do
+  guard :rake, :task => 'acceptance' do
+    watch(%r{^spec\/acceptance\/.+\.rb$})
+  end
+end