Will Yardley

Are there any releases for which `F4E789204D206F89` is still valid, and if so, is that accessible from anywhere?

@michaelklishin I have to double check - module’s default behavior actually ships 3.3.x (from the vendors’ repos) on certain platforms, tho I guess in that case it will probably be...

@juniorsysadmin I agree that that's probably the most secure way. Do you have time / inclination to throw up a PR to switch it to this pattern?

FWIW, I added #888 which improves things in certain ways, but may actually make this worse in other ways. I agree that the interface could be more consistent. Once the...

@kwisatz: Yes, I think that's the cleanest way to make it work as it should (and to make all the logging statements consistent), only downsides are a) would take some...

May want to wait for #878 for that - I’d like to get 11.1 out and then we can ship the breaking release. I think #884 was an incremental step...

It does mean that we probably should continue without #884 either for now. Let’s keep this open and rebase / merge after 11.1.

@TwizzyDizzy can you resolve the conflicts from #886, which will ship first in a non-breaking release?

After #878 also won't need to raise min puppet version anymore, because it includes that.

> Hence, I don't think there is any need to raise the minimum required puppet version either. > On the other hand, one might still vote for raising the minimum...