rspec-puppet-yaml 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 635d74aae6ca5cabe2a88ca0d09e1c6f0c6cc099
+  data.tar.gz: 379c30071212890a4b04238c11fc87a41b4372c7
+SHA512:
+  metadata.gz: 446246c48b97c01201621d793abef3b3e1bfde738da4016003dc6dec2c1ce003de34021d9f5e47c4c3757b8e80772abe14bc1f1075844fda5c5dfdadbf2d92ae
+  data.tar.gz: 8a5c2d3ac8c5d7a43f4cea2abf8746d29365cba4ce4a76aadf3788c0cd723c2e5a7af9267f227891488c88ac810bc603e2e10a341e83a72a642e2094cedb052f

data/.gitignore

@@ -0,0 +1,16 @@
+.*.sw[op]
+.metadata
+.yardwarns
+/.bundle/
+/.idea/
+/.vagrant/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/tmp/
+/vendor/
+
+# rspec failure tracking
+.rspec_status

data/.inch.yml

@@ -0,0 +1,4 @@
+files:
+  # define files included in the analysis (defaults to ["{app,lib}/**/*.rb"])
+  included:
+    - lib/**/*.rb

data/.rspec

@@ -0,0 +1,2 @@
+--format documentation
+--color

data/.travis.yml

@@ -0,0 +1,29 @@
+sudo: false
+language: ruby
+cache: bundler
+before_install:
+  - bundle -v
+  - gem update --system
+  - gem install bundler -v 1.15.4
+  - gem --version
+  - bundle -v
+matrix:
+  fast_finish: true
+  include:
+    - rvm: 2.4.1
+      bundler_args: --without system_tests
+      script:
+        - 'bundle exec rake spec'
+        - 'bundle exec yard'
+branches:
+  only:
+    - master
+    - /^v\d/
+notifications:
+  email: false
+deploy:
+  - provider: pages
+    skip_cleanup: true
+    github_token: $GITHUB_TOKEN
+    on:
+      branch: master

data/.yardopts

@@ -0,0 +1,2 @@
+--markup markdown
+--output-dir docs/

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,75 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at
+github-rspec-puppet-yaml@kimballstuff.com. All complaints will be reviewed and
+investigated and will result in a response that is deemed necessary and
+appropriate to the circumstances. The project team is obligated to maintain
+confidentiality with regard to the reporter of an incident.  Further details of
+specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,6 @@
+source "https://rubygems.org"
+
+git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
+
+# Specify your gem's dependencies in rspec-puppet-yaml.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,93 @@
+PATH
+  remote: .
+  specs:
+    rspec-puppet-yaml (0.1.0)
+      deep_merge (~> 1.1)
+      rspec-puppet (~> 2.6)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    deep_merge (1.1.1)
+    diff-lcs (1.3)
+    facter (2.5.0)
+    facterdb (0.3.12)
+      facter
+      jgrep
+    fast_gettext (1.1.0)
+    gettext (3.2.4)
+      locale (>= 2.0.5)
+      text (>= 1.3.0)
+    gettext-setup (0.26)
+      fast_gettext (~> 1.1.0)
+      gettext (>= 3.0.2)
+      locale
+    hiera (3.4.0)
+    jgrep (1.5.0)
+    json (2.1.0)
+    locale (2.1.2)
+    mcollective-client (2.11.2)
+      json
+      stomp
+      systemu
+    metaclass (0.0.4)
+    mocha (1.1.0)
+      metaclass (~> 0.0.1)
+    puppet (5.1.0)
+      facter (> 2.0, < 4)
+      gettext-setup (>= 0.10, < 1)
+      hiera (>= 3.2.1, < 4)
+      locale (~> 2.1)
+    puppet-lint (2.3.0)
+    puppet-strings (1.1.0)
+      yard (~> 0.9.5)
+    puppet-syntax (2.4.1)
+      rake
+    puppetlabs_spec_helper (2.3.2)
+      mocha (~> 1.0)
+      puppet-lint (~> 2.0)
+      puppet-syntax (~> 2.0)
+      rspec-puppet (~> 2.0)
+    rake (12.0.0)
+    rspec (3.6.0)
+      rspec-core (~> 3.6.0)
+      rspec-expectations (~> 3.6.0)
+      rspec-mocks (~> 3.6.0)
+    rspec-core (3.6.0)
+      rspec-support (~> 3.6.0)
+    rspec-expectations (3.6.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.6.0)
+    rspec-mocks (3.6.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.6.0)
+    rspec-puppet (2.6.8)
+      rspec
+    rspec-puppet-facts (1.8.0)
+      facter
+      facterdb (>= 0.3.0)
+      json
+      mcollective-client
+      puppet
+    rspec-support (3.6.0)
+    stomp (1.4.4)
+    systemu (2.6.5)
+    text (1.3.1)
+    yard (0.9.9)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.15)
+  json (~> 2.1)
+  puppet (~> 5)
+  puppet-strings (~> 1)
+  puppetlabs_spec_helper (~> 2.3)
+  rake (~> 12.0)
+  rspec-puppet-facts (~> 1.8)
+  rspec-puppet-yaml!
+  yard (~> 0.9)
+
+BUNDLED WITH
+   1.15.4

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2017 William Kimball
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.