[MODULES-5896] Implement Rubocop in Reboot - Puppet Tickets

XML

Word

Printable

Template:
customfield_10700 219691
Acceptance Criteria:
Hide

Merge or close all PRs, do a release.

Run Rubocop

Set up Rubocop to be used by default by the module

Test against all currently supported platforms, as listed on the Forge: https://forge.puppet.com/puppetlabs/reboot/compatibility

Release the updated module with documentation updated to outline the changes.
Show
Merge or close all PRs, do a release. Run Rubocop Set up Rubocop to be used by default by the module Test against all currently supported platforms, as listed on the Forge: https://forge.puppet.com/puppetlabs/reboot/compatibility Release the updated module with documentation updated to outline the changes.
Epic Link:
PDK Convert Windows Modules
Team:
Windows
Sprint:
Windows Kanban

As a developer I want reboot to have Rubocop implemented so that my code follows the Ruby style guide.

For this story to be implemented the following tasks should be performed:

Merge all PR's that can be merged on the module.
Any PR's that can't be merged should be closed with the reason given to the PR author.
Release the module, so there is a baseline release before Rubocop is applied.
Rubocop should be run against the code in the module.
Regex's should be checked so that the backslash issue that happened on MySQL doesn't recur (see: this JIRA ticket).
Rubocop should automatically run on the module in the future, so that all future releases of the module have Rubocop automatically applied.

relates to

MODULES-6598 puppet_pot_generator: semantic_puppet dependency no longer necessary

MODULES-3975 Reboot - Fix conditionals in Windows provider