Puppet Community

<@U1PC2RAH0> <https://github.com/puppetlabs/puppet-lint/pull/87>

craig: I think before <https://github.com/puppetlabs/puppet-lint/pull/85> is merged we should think about the question is posted above, how do we handle puppet-lint vs puppet-lint-top_scope_facts-check vs voxpupuli-puppet-lint-plugins for existing installations

My original thought was just to removed it from the vox gem

With the version drop there is no reason not to upgrade to v3

hmm interesting, I mean is there even a current way to deal with potential clashes / priority or would it be down to setting the template to ignore checks?

Would it work if we did a breaking change for the vox gem <@U1PC2RAH0>

and set a requirement for puppet-lint vX?

I think for puppet-lint some agreement should be made on the direction and how to do gem development

using litmus for gems is just a horrible idea IMHO so why not cucumber? <https://github.com/puppetlabs/puppet-lint/pull/89>

that means you can easily run it locally as well

wow, cucumber, blast from the past :slightly_smiling_face:

i thought i’d taken litmus out of puppet-lint to be honest.. we don’t need anything above rspec for now

I guess you could also run it natively with rspec

but additionally I think test tooling may be slightly out of scope for this particular change

(certainly a topic we are wanting to talk about though)

IMHO you must get rid of the dependency on puppetlabs_spec_helper in puppet-lint

for puppet-lint? have you got an example?

<https://github.com/puppetlabs/puppet-lint/blob/dbc093c87cc001545c783e94e8d0d94cc290dfd4/Gemfile#L20>

I think a new voxpupuli-puppet-lint-plugins release that requires puppet-lint 3.x will help for the plugin foobar

that's why I want to get rid of litmus there

if both mmkinst plugins are vendored into puppet-lint and dropped from our gem

Seeing the paragraph about ERB, what is the future of ERB templates in Puppet? Not for Puppet 8, but in general?

No changes to ERB support on the roadmap as far as I know

fwiw, the ERB changes here will not matter at all to you unless you're writing Ruby code that renders templates

For note it was because customer had put a capital at the start of what was meant to be a resource declaration and that then made it a resource default, which the linter then added to loops for both resource and default

<https://github.com/voxpupuli/puppet-lint-trailing_comma-check/issues/31#issuecomment-1446655427>