puppet-retrospec 0.12.1 → 0.12.2

data/spec/fixtures/manifests/includes-defines.pp

@@ -1,26 +0,0 @@
-define webinstance{
-
-  include class1
-  include class2
-  include class3
-
-
-  require class4
-  require class5
-
-  $var1 = 'true'
-
-  file{"dummytest":
-    ensure => directory
-
-  }
-
-  file{"dummytest":
-    ensure => directory
-  }
-
-  if $var1 == 'true'{
-    include class6
-  }
-
-}

data/spec/fixtures/modules/concat/CHANGELOG.md

@@ -1,257 +0,0 @@
-##2015-06-02 - Supported Release 1.2.3
-###Summary
-
-This release includes a README fix to document correct behavior of fragment target parameter.
-
-####Bugfixes
-
-- README Fix to correctly document how a fragment $target param should work.
-
-##2015-05-12 - Supported Release 1.2.2
-###Summary
-
-This release includes a bugfix.
-
-####Bugfixes
-- Fixes a bug introduced by MODULES-1700, in handling default retrieval of fragment backup parameter.
-
-##2015-04-14 - Supported Release 1.2.1
-###Summary
-
-This release includes bugfixes, test improvements, and a rewritten README.
-
-####Bugfixes
-
-- Verifies existence of $is_pe before using it.
-- Adds validation for $order param to not allow restricted characters.
-- Sets the group id on Fragments for versions of Facter that contain the $gid fact.
-- Sets the script group to 0 if the script is owned by root.
-- Explicitly sets script and concat directories to the same owner and group.
-- Re-adds support for fragment backup, so that static compiler can work with filebucket (MODULES-1700).
-
-##2015-02-17 - Supported Release 1.2.0
-###Summary
-
-This release includes a number of bugfixes and adds support for running a validation command when using puppet >= 3.5.0.
-
-####Features
-- Support running a validation command for Puppet >= 3.5.0
-
-####Bugfixes
-- Reset poisoned defaults from Exec
-- Use concatfragments.rb on AIX since it doesn't support print0
-- Make sure ruby is in the path for PE (MODULES-1456)
-- Fix missing method for check_is_owned_by for windows (MODULES-1764)
-- Fix sort by numeric
-
-##2014-10-28 - Supported Release 1.1.2
-###Summary
-
-This release includes bugfixes and test improvements. The module was tested against SLES10 and SLES12 and found to work against those platforms with no module improvements. Metadata was updated to include those as supported platforms.
-
-####Bugfixes
-- newline didn't work for Windows and Solaris. This has been fixed.
-- Install certs on Windows for acceptance tests
-- Update tests to work with strict variables (no module updates were required)
-- Update tests to work on Windows
-- Fix typo in CHANGELOG.md
-
-##2014-09-10 - Supported Release 1.1.1
-###Summary
-
-This is a bugfix release, and the first supported release of the 1.1.x series.
-
-####Bugfixes
-- Make the `$order` parameter default to a string and be validated as an integer
-  or a string
-- Use the ruby script on Solaris to not break Sol10 support
-- Add quotes to the ruby script location for Windows
-- Fix typos in README.md
-- Make regex in concat::setup case-insensitive to make it work on Windows
-- Make sure concat fragments are always replaced
-- Fix validation to allow `$backup` to be a boolean
-- Remove dependency on stdlib 4.x
-- Fix for lack of idempotency with `ensure => 'absent'`
-- Fix tests and spec_helper
-- Synchronized files for more consistency across modules via modulesync
-
-##2014-05-14 - Release 1.1.0
-###Summary
-
-This release is primarily a bugfix release since 1.1.0-rc1.
-
-####Features
-- Improved testing, with tests moved to beaker
-
-####Bugfixes
-- No longer attempts to set fragment owner and mode on Windows
-- Fix numeric sorting
-- Fix incorrect quoting
-- Fix newlines
-
-##2014-01-03 - Release 1.1.0-rc1
-###Summary
-
-This release of concat was 90% written by Joshua Hoblitt, and the module team
-would like to thank him for the huge amount of work he put into this release.
-
-This module deprecates a bunch of old parameters and usage patterns, modernizes
-much of the manifest code, simplifies a whole bunch of logic and makes
-improvements to almost all parts of the module.
-
-The other major feature is windows support, courtesy of luisfdez, with an
-alternative version of the concat bash script in ruby.  We've attempted to
-ensure that there are no backwards incompatible changes, all users of 1.0.0
-should be able to use 1.1.0 without any failures, but you may find deprecation
-warnings and we'll be aggressively moving for a 2.0 to remove those too.
-
-For further information on deprecations, please read:
-https://github.com/puppetlabs/puppetlabs-concat/blob/master/README.md#api-deprecations
-
-####Removed
-- Puppet 0.24 support.
-- Filebucket backup of all file resources except the target concatenated file.
-- Default owner/user/group values.
-- Purging of long unused /usr/local/bin/concatfragments.sh
-
-###Features
-- Windows support via a ruby version of the concat bash script.
-- Huge amount of acceptance testing work added.
-- Documentation (README) completely rewritten.
-- New parameters in concat:
- - `ensure`: Controls if the file should be present/absent at all.
- - Remove requirement to include concat::setup in manifests.
- - Made `gnu` parameter deprecated.
- - Added parameter validation.
-
-###Bugfixes
- - Ensure concat::setup runs before concat::fragment in all cases.
- - Pluginsync references updated for modern Puppet.
- - Fix incorrect group parameter.
- - Use $owner instead of $id to avoid confusion with $::id
- - Compatibility fixes for Puppet 2.7/ruby 1.8.7
- - Use LC_ALL=C instead of LANG=C
- - Always exec the concatfragments script as root when running as root.
- - Syntax and other cleanup changes.
-
-##2014-06-25 - Supported Release 1.0.4
-###Summary
-
-This release has test fixes.
-
-####Features
-- Added test support for OSX.
-
-####Bugfixes
-
-####Known bugs
-
-* Not supported on Windows.
-
-##2014-06-04 - Release 1.0.3
-###Summary
-
-This release adds compatibility for PE3.3 and fixes tests.
-
-####Features
-- Added test support for Ubuntu Trusty.
-
-####Bugfixes
-
-####Known bugs
-
-*Not supported on Windows.
-
-##2014-03-04 - Supported Release 1.0.2
-###Summary
-
-This is a supported release. No functional changes were made from 1.0.1.
-
-####Features
-- Huge amount of tests backported from 1.1.
-- Documentation rewrite.
-
-####Bugfixes
-
-####Known Bugs
-
-* Not supported on Windows.
-
-
-##2014-02-12 - 1.0.1
-###Summary
-
-Minor bugfixes for sorting of fragments and ordering of resources.
-
-####Bugfixes
-- LANG => C replaced with LC_ALL => C to reduce spurious recreation of
-fragments.
-- Corrected pluginsync documentation.
-- Ensure concat::setup always runs before fragments.
-
-
-##2013-08-09 - 1.0.0
-###Summary
-
-Many new features and bugfixes in this release, and if you're a heavy concat
-user you should test carefully before upgrading.  The features should all be
-backwards compatible but only light testing has been done from our side before
-this release.
-
-####Features
-- New parameters in concat:
- - `replace`: specify if concat should replace existing files.
- - `ensure_newline`: controls if fragments should contain a newline at the end.
-- Improved README documentation.
-- Add rspec:system tests (rake spec:system to test concat)
-
-####Bugfixes
-- Gracefully handle \n in a fragment resource name.
-- Adding more helpful message for 'pluginsync = true'
-- Allow passing `source` and `content` directly to file resource, rather than
-defining resource defaults.
-- Added -r flag to read so that filenames with \ will be read correctly.
-- sort always uses LANG=C.
-- Allow WARNMSG to contain/start with '#'.
-- Replace while-read pattern with for-do in order to support Solaris.
-
-####CHANGELOG:
-- 2010/02/19 - initial release
-- 2010/03/12 - add support for 0.24.8 and newer
-             - make the location of sort configurable
-             - add the ability to add shell comment based warnings to
-               top of files
-             - add the ablity to create empty files
-- 2010/04/05 - fix parsing of WARN and change code style to match rest
-               of the code
-             - Better and safer boolean handling for warn and force
-             - Don't use hard coded paths in the shell script, set PATH
-               top of the script
-             - Use file{} to copy the result and make all fragments owned
-               by root.  This means we can chnage the ownership/group of the
-               resulting file at any time.
-             - You can specify ensure => "/some/other/file" in concat::fragment
-               to include the contents of a symlink into the final file.
-- 2010/04/16 - Add more cleaning of the fragment name - removing / from the $name
-- 2010/05/22 - Improve documentation and show the use of ensure =>
-- 2010/07/14 - Add support for setting the filebucket behavior of files
-- 2010/10/04 - Make the warning message configurable
-- 2010/12/03 - Add flags to make concat work better on Solaris - thanks Jonathan Boyett
-- 2011/02/03 - Make the shell script more portable and add a config option for root group
-- 2011/06/21 - Make base dir root readable only for security
-- 2011/06/23 - Set base directory using a fact instead of hardcoding it
-- 2011/06/23 - Support operating as non privileged user
-- 2011/06/23 - Support dash instead of bash or sh
-- 2011/07/11 - Better solaris support
-- 2011/12/05 - Use fully qualified variables
-- 2011/12/13 - Improve Nexenta support
-- 2012/04/11 - Do not use any GNU specific extensions in the shell script
-- 2012/03/24 - Comply to community style guides
-- 2012/05/23 - Better errors when basedir isnt set
-- 2012/05/31 - Add spec tests
-- 2012/07/11 - Include concat::setup in concat improving UX
-- 2012/08/14 - Puppet Lint improvements
-- 2012/08/30 - The target path can be different from the $name
-- 2012/08/30 - More Puppet Lint cleanup
-- 2012/09/04 - RELEASE 0.2.0
-- 2012/12/12 - Added (file) $replace parameter to concat

data/spec/fixtures/modules/concat/CONTRIBUTING.md

@@ -1,220 +0,0 @@
-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:
-
-    * Pre-requisites:
-
-      - Make sure you have a [GitHub account](https://github.com/join)
-
-      - [Create a ticket](https://tickets.puppetlabs.com/secure/CreateIssue!default.jspa), or [watch the ticket](https://tickets.puppetlabs.com/browse/) you are patching for.
-
-    * 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
----------------
-
-Our 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://puppetlabs.com/community/get-help)
-
-* [Writing tests](http://projects.puppetlabs.com/projects/puppet/wiki/Development_Writing_Tests)
-
-* [Patchwork](https://patchwork.puppetlabs.com)
-
-* [General GitHub documentation](http://help.github.com/)
-
-* [GitHub pull request documentation](http://help.github.com/send-pull-requests/)
-