Update cookbook with latest alignments + styles (#8)

* cookstyle lints + alignments to tecRacer OS standards

* update md files

* renaming + adding kitchen configs

* add amazon to recipe + add centos-6 to kitchen

* add centos-6 to dokken

* fix pid_one_command for centos-6

* add github templates

* remove amazon linux + centos-6 from kitchen testing

* add codeowners

* update to version 3.0.0

* fix small wrong alignments and versions

* fix dokken env

Author: Patrick Schaumburg

.github/CODEOWNERS

@@ -0,0 +1,3 @@
+# Order is important. The last matching pattern has the most precedence.
+
+* @tecracer-chef-cookbooks/tr-opensource-maintainer

.github/ISSUE_TEMPLATE/BUG_TEMPLATE.md

@@ -0,0 +1,26 @@
+---
+name: 🐛 Bug Report
+about: If something isn't working as expected 🤔.
+labels: "bug"
+---
+
+### Cookbook version
+[Version of the cookbook where you are encountering the issue]
+
+### Chef-client version
+[Version of chef-client in your environment]
+
+### Platform Details
+[Operating system distribution and release version. Cloud provider if running in the cloud]
+
+### Scenario:
+[What you are trying to achieve and you can't?]
+
+### Steps to Reproduce:
+[If you are filing an issue what are the things we need to do in order to repro your problem? How are you using this cookbook or any resources it includes?]
+
+### Expected Result:
+[What are you expecting to happen as the consequence of above reproduction steps?]
+
+### Actual Result:
+[What actually happens after the reproduction steps? Include the error output or a link to a gist if possible.]

.github/ISSUE_TEMPLATE/ENHANCEMENT_REQUEST_TEMPLATE.md

@@ -0,0 +1,17 @@
+---
+name: 🚀 Enhancement Request
+about: I have a suggestion (and may want to implement it 🙂)!
+labels: "new feature"
+---
+
+### Describe the Enhancement:
+<!---  What you are trying to achieve that you can't? -->
+
+### Describe the Need:
+<!---  What kind of user do you believe would utilize this enhancement, and how many users might want this functionality -->
+
+### Current Alternative
+<!--- Is there a current alternative that you can utilize to workaround the lack of this enhancement -->
+
+### Can We Help You Implement This?:
+<!---  The best way to ensure your enhancement is built is to help implement the enhancement yourself. If you're interested in helping out we'd love to give you a hand to make this possible. Let us know if there's something you need. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+### Description
+
+[Describe what this change achieves]
+
+### Issues Resolved
+
+[List any existing issues this PR resolves]
+
+### Check List
+
+- [ ] All tests pass.
+- [ ] New functionality includes testing.
+- [ ] New functionality has been documented in the README if applicable

.github/workflows/kitchen-test.yml

@@ -0,0 +1,29 @@
+name: kitchen-test
+
+on:
+  pull_request:
+  push:
+    branches:
+      - master
+
+jobs:
+  dokken:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        os: ['amazon2', 'centos-7', 'centos-8', 'debian-9', 'debian-10', 'opensuse-leap-15', 'ubuntu-1604', 'ubuntu-1804', 'ubuntu-2004']
+        suite: ['default']
+      fail-fast: false
+    steps:
+      - name: Check out code
+        uses: actions/checkout@master
+      - name: Install Chef
+        uses: actionshub/chef-install@master
+      - name: Run test-kitchen
+        run: |
+          kitchen test ${SUITE}-${OS} -d always
+        env:
+          SUITE: ${{matrix.suite}}
+          OS: ${{matrix.os}}
+          CHEF_LICENSE: accept-no-persist
+          KITCHEN_LOCAL_YAML: kitchen.dokken.yml

.github/workflows/linting.yml

@@ -0,0 +1,27 @@
+name: linting
+
+on:
+  pull_request:
+  push:
+    branches:
+      - master
+
+jobs:
+  cookstyle:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Check out code
+      uses: actions/checkout@master
+    - name: Install Chef
+      uses: actionshub/chef-install@master
+    - name: Run cookstyle
+      run: cookstyle
+      env:
+        CHEF_LICENSE: accept-no-persist
+  mdl:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out code
+        uses: actions/checkout@master
+      - name: Run Markdown Lint
+        uses: actionshub/markdownlint@master

.ruby-version

@@ -1,21 +1,37 @@
-# Change Log
+# Changelog
 
-## [v1.1.0](https://github.com/jjasghar/chef-vmware-tools/tree/v1.1.0)
+## [3.0.0] - 2020-05-06
 
-[Full Changelog](https://github.com/jjasghar/chef-vmware-tools/compare/v1.0.1...v1.1.0)
+* update minimum required chef version to 15.0 (BREAKING CHANGE)
+* update metadata.rb with new contents
+* update attributes + recipe files with style fixes
+* update changelog, contributing, readme and testing
+* add GitHub templates for bugs and pull requests
+* add GitHub Actions for linting and kitchen test
+* add Codeowners
+* add kitchen configs for ec2, dokken, vra
+* rename .kitchen files to kitchen
+* remove .ruby-version
 
-**Merged pull requests:**
+## [2.1.0] - 2018-05-21
 
-- Added always be updating. [\#2](https://github.com/jjasghar/chef-vmware-tools/pull/2) ([jjasghar](https://github.com/jjasghar))
+* Bumped version of windows tools
 
-## [v1.0.1](https://github.com/jjasghar/chef-vmware-tools/tree/v1.0.1) (2018-02-05)
-[Full Changelog](https://github.com/jjasghar/chef-vmware-tools/compare/v1.0.0...v1.0.1)
+## [2.0.0] - 2018-04-23
 
-## [v1.0.0](https://github.com/jjasghar/chef-vmware-tools/tree/v1.0.0) (2018-02-05)
-**Merged pull requests:**
+* First pass at the windows rebooting.
 
-- 1.0.0 Release [\#1](https://github.com/jjasghar/chef-vmware-tools/pull/1) ([jjasghar](https://github.com/jjasghar))
+## [1.1.0] - 2018-02-06
 
+* Added a flag to change to update always, instead of just installing.
 
+## [1.0.1] - 2018-02-06
 
-\* *This Change Log was automatically generated by [github_changelog_generator](https://github.com/skywinder/Github-Changelog-Generator)*
+* Added always be updating
+
+## [1.0.0] - 2018-02-05
+
+* Updated cookbook to open-vm-tools
+* Updated for both Debian and RPM based distros
+* Added Windows support
+* Added tests and test-kitchen support

CHANGELOG.md

@@ -1,14 +1,16 @@
-Contributing
-============
+# Contributing
+
+---
 
 Steps
------
 
-Thanks for your interest in gelsinger! If you'd like to help out please:
+---
+
+Thanks for your interest in contributing! If you'd like to help out please:
 
 1. Fork it
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Add tests for the new feature; ensure they pass (`rake`)
-4. Commit your changes (`git commit -am 'Add some feature'`)
-5. Push to the branch (`git push origin my-new-feature`)
-6. Create a new Pull Request
+1. Create your feature branch (`git checkout -b my-new-feature`)
+1. Add tests for the new feature; ensure they pass (`rake`)
+1. Commit your changes (`git commit -am 'Add some feature'`)
+1. Push to the branch (`git push origin my-new-feature`)
+1. Create a new Pull Request

CONTRIBUTING.md

@@ -6,38 +6,44 @@ Chef cookbook for installing [VMware tools](https://docs.vmware.com/en/VMware-To
 
 ## Attributes
 
-- `default['vmware-tools']['update']` - default set to `true`, you know you want the newest _always_.
-- `default['vmware-tools']['windows_reboot']` - default set to `true`, and if put at the first cookbook you'll reboot then run the rest of the `run_list`.
-- `default['vmware-tools']['url']` - The location to get the Windows VMware-Tools executable from.
-- `default['vmware-tools']['version']` - The version of the Windows VMware-Tool.
+- `default['vmware-tools']['update']` - default set to `true`, you know you want
+  the newest _always_.
+- `default['vmware-tools']['windows_reboot']` - default set to `true`, and if
+  put at the first cookbook you'll reboot then run the rest of the `run_list`.
+- `default['vmware-tools']['url']` - The location to get the Windows VMware-Tools
+  executable from.
+- `default['vmware-tools']['version']` - The version of the Windows VMware-Tools.
 
 ## Usage
 
 ### vmware-tools::default
 
-The default recipe will install [open-vm-tools](https://github.com/vmware/open-vm-tools) of on a CentOS/Debian based machine. If you run this on Windows it install the public VMware Tools executable from https://packages.vmware.com.
+The default recipe will install [open-vm-tools](https://github.com/vmware/open-vm-tools)
+  of on a CentOS/Debian based machine. If you run this on Windows it installs the
+  public VMware Tools executable from [packages.vmware.com](https://packages.vmware.com).
 
-If you have a specific place you want to install your Windows based VMware Tools from, override the `default['vmware-tools']['url']` and `default['vware-tools']['version']` in the default attributes.
+If you have a specific place you want to install your Windows based VMware Tools
+  from, override the `default['vmware-tools']['url']`
+  and `default['vware-tools']['version']` in the default attributes.
 
 ## Testing
 
 For more details look at the [TESTING.md](./TESTING.md).
 
 ## License & Authors
 
-If you would like to see the detailed LICENCE click [here](./LICENCE).
+**Author:** tecRacer Opensource Team ([opensource@tecracer.de](mailto:opensource@tecracer.de))
+**Original Author:** JJ Asghar [GitHub](https://github.com/jjasghar)
+**Original Author:** Andrew Fraley [GitHub](https://github.com/andrewfraley/)
 
-- Author: JJ Asghar <jj@chef.io>
-- Author: https://github.com/andrewfraley/
-
-```text
-Copyright:: JJ Asghar
+**Copyright:** 2020, tecRacer Group
 
+```
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-http://www.apache.org/licenses/LICENSE-2.0
+    http://www.apache.org/licenses/LICENSE-2.0
 
 Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,