puppet-lint and rubocop checks #1140
Replies: 5 comments 1 reply
-
Comment from @genebean : FWIW, puppet-lint plugin wise, I have traditionally used these: puppet-lint-absolute_template_path |
Beta Was this translation helpful? Give feedback.
-
Comment from Tim Muesel: On Vox Pupuli we use: $ bundle list | grep puppet-lint-
|
Beta Was this translation helpful? Give feedback.
-
Comment from @yachub : Even though options in .puppet-lint.rc are configurable in .sync.yml through Rakefile.linter_fail_on_warnings, I think enabling --fail-on-warnings as a default via changing fail_on_warnings would be a good idea, otherwise any findings caught by the puppet-lint gems results in a successful test. Specifically thinking about CI with pull requests in regards to this. |
Beta Was this translation helpful? Give feedback.
-
Vox Pupuli now also uses puppet-lint-optional_default-check on all modules. Modules with full puppet-strings coverage also have puppet-lint-param-docs. |
Beta Was this translation helpful? Give feedback.
-
@sanfrancrisko how can we move this forward? Vox Pupuli publishes a gem that pulls in all related linter plugins: https://rubygems.org/gems/voxpupuli-puppet-lint-plugins and I think it would be really good for the puppet ecosystem if pdk uses this plugin as well (in addition to setting fail_on_warnings). |
Beta Was this translation helpful? Give feedback.
-
Originally raised: https://tickets.puppetlabs.com/browse/PDK-1700
We should add/create several puppet-lint plugins to the default install. We should also maintain a set of Puppet specific rubocop rules like https://github.com/chef/cookstyle/tree/master/lib/rubocop/cop/chef
Lint checks:
Rubocops
Beta Was this translation helpful? Give feedback.
All reactions