Major cleanup of testing & documentation

[detjensrobert]

Description

• Adds full InSpec testing for Kitchen suite
• Adds complete documentation for resources
• Refactors ChefSpec tests for full coverage
• Refactors test recipes and suites
• Idempotency fixes for test recipes
• Updates old conventions to modern standards

Breaking Changes

• Removed support for:
  • Amazon Linux
  • Amazon Linux 2
  • Debian
  • Ubuntu

Issues Resolved

Fixes #123 #121

Check List

• All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
• New functionality includes testing.
• New functionality has been documented in the README if applicable
• All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

---

Signed-off-by: Robert Detjens [email protected]

[detjensrobert]

SELinux testing does not work with Dokken / Docker and breaks GHCI due to a reboot needed to fully enable SEL. Should the GHCI Dokken testing be removed or disabled?

[ramereth]

SELinux testing does not work with Dokken / Docker and breaks GHCI due to a reboot needed to fully enable SEL. Should the GHCI Dokken testing be removed or disabled?

The only way to do this is via some runner which supports Virtualbox+Vagrant. Unfortunately GH Actions don't support nested virtualization yet so that's not really an option. The other option is doing this from a self hosted runner but I doubt Chef Inc would want to do that.

Perhaps the best option is to just remove the dokken ci portion of this and also remove the dokken yaml in the meantime and force use of Vagrant? I'd want to see what @tas50 thinks however.

[ramereth]

LGTM