Puppet Community

1. <https://github.com/voxpupuli/puppet-wildfly/pull/341>

2. <https://github.com/voxpupuli/puppet-wildfly/pull/343>

hrm, when I've BUNDLE_WITHOUT=development it would be nice if bundler actually ignores the development group

it poops itself when the gem group contains one gem that requires a newer ruby version than available :(

it bundles without, but it still analyzes everything

have been bitten by this waaaay to many times

Zhenech: and now you will present me a solution for this? 

Can I get some feedback at <https://github.com/voxpupuli/beaker/pull/1906> ?

The fact that bundler still observed constraints for gems whose group is excluded/without is one of the reasons why we created separate Gemfiles for puppet vs acceptance/Gemfile.

Sure seems like a bundler bug. It would be nice to not have to do that 

&gt; Bundling without doesn’t re-resolve the Gemfile.lock because then we’d have a superposition of 2 Gemfile.locks that were incompatible with each other. I think there’s some tools like bundle-compose or bootboot that could help, but I don’t have a lot of experience with them.

RFC: what about adding `c.filter_run_when_matching focus: true` to our `spec_helper.rb` by default? This allows to focus on one example in RSpec test using `focus: true` meta or `fcontext`/`fit` (also rubocop exception may be good to add to the line).

I’m not sure about any cons of this though..

the only I can imagine - it’s easy to forget that you were working on focused examples and PR it in.. if rubocop disable comment is present, then no way to catch it except grepping explicitly.

Somehow I see some questionable rubocop settings :thinking_face: e.g. it tries to remove comma after the last item in a Hash in RSpec example. Also it tends to leave the `.` in the end of the previous line instead of beginning of next one. Is it something changed recently?

I mean things like that:
```it do
  <http://is_expected.to|is_expected.to> contain_foo('foo').
    with_ensure('present).
    with_value(true)
end```

usually it was always in the beginning of a line (`.with_ensure(...)`)

Yeah.. I was quite surprised.. though now I think it might be something in my VSCode/Ruby LSP. Will check from CLI soon

Ah, do you mean focus? That’s quite useful. Huge time saver

So we have a different rubocop config for gems vs puppet modules.

Maybe they have different configs for the dot

I’ll recheck and update here. Meanwhile my systemd PR is ready for review. Cannot say I like the approach, but it should do the trick.

Also there is a lot of improvements pending after. The types I introduced should be used in other places (and more types should be introduced I believe)