the longer you wait the more challenging it becomes because you might need to update multiple modules at once, but it's easy to test

what's the puppet version you're using?

8.10

So.. snapshot puppet master VM, update everything, in case of explosions can go back to snapshot and continue where I left?

that sounds horrible

I knew he'd say that.

I would create a new code environment, update all modules, write tests for it or run agents with noop against it, do that until it works, merge it, then set up automation to notify you about module updates

there will be explosions when all of your modules are that ancient

What's the practical impact on invalid modules, will they still work to some extent but simply lose certain functions or will they cease to work at all?

the version range indicates which version of a dependency might have been tested, that's about it

but you can assume that newer modules don't work with stdlib < 9

as mentioned: create a branch, update modules in Puppetfile and then use onceover for testing the control repo.

bastelfreak: style fix for your eula blog https://github.com/voxpupuli/voxpupuli.github.io/pull/473

[thread]: he's gonna have a lot of queued up alerts when he gets back, isn't he

deadrom: that's in undefined behaviour territory. What happens when you use code written for an older language spec or older modules? It could be a) by happy accident, it works just fine; b) mostly works but doesn't take advantage of improvements; c) silent errors in that module but things appear to work; d) that module stops working; d) it breaks the entire puppet run

deadrom: basically just like any programming language or interface, it all depends on what language features are used.

One can't disable this block, shall I enclose it in another parameter? https://github.com/voxpupuli/puppet-postfix/blob/master/manifests/service.pp#L32-L37

it's no longer /usr/sbin in the latest rpm

If that affects only specific OS release, I’d make it a parameter and move it to Hiera.

If they did this breaking change within single OS lifetime, then you need to know what rpm version is installed/where the file is (or just use Exec to ensure it’s still available by the old path while staying on this OS release)

I guess it might change on CentOS only, because of the rolling release model. Other RHEL-likes shouldn’t be that crazy to switch it in the middle of lifetime

I think this is a safe change https://github.com/voxpupuli/puppet-postfix/pull/423

It changed on Fedora

module seems dated, mix of params and hiera

Commented in the PR

I would need your guidance tomorrow, I just used my fork to stop the bleed, because service would fail

sure, let me add the REFERENCE.md regen command to the PR comment

Zhenech: I kinda expected the foreman packages in https://deb.theforeman.org/pool/plugins/nightly/r/, after your merged the PR to deb/develop. Is my assumption incorrect or is something still missing?