This message was deleted.
# puppet
s
This message was deleted.
s
This module dependency say
puppetlabs/stdlib (>=2.3.0 <5.0.0)
, I guess you are out of bound 🙂
d
c
thanks, @smortex. I guess I need to hunt a different way to manage network interfaces, then
s
The module was not updated for some years, but the maintainer still show activity on GitHub, so maybe you can send him a PR to fix the module and ask him to do a release? Also as you say, maybe an alternative might be a good option. I can't tell 🤷
c
I’ve been handed a legacy codebase and have been tasked with bringing it up to date
👍 1
they already were using it. I didn’t know about the introduced incompatability
s
It was introduced in stdlib 9.0.0 I think (I did remove a lot of legacy outdated code), so maybe using stdlib 8.x might help a bit… but regular updates to maintain support of newer dependencies is a good practice so the module defenitively need some love.
c
I have other modules that require newer stdlib, so… I’d rather stay new if I have to write my own network module. ¯\_(ツ)_/¯
s
Yup. In case you missed it, stdlib-9.0.0 was released not-so-long ago and you should expect some breakage until the modules depending on it are updated te be compatible. Good luck!
c
lol. I can’t tell if that was sarcastic or not. :D
s
No 🙂 I imagine you have quite a lot of work on the table, so genuinely hoping you go through it without too much pain!
c
Is there a place where the puppet team has shared common recipes for modernizing modules to be compatible with stdlib-9.0.0? I guess folks could look at the release notes and see the removed functions and individually look at (or infer) their suggested replacements. But a concise upgrade guide would be nice.