[Puppet Users] Upcoming Forge IP Address Change

On Monday, October 26th, 2020 we will be updating the `forge.puppet.com` and `forgeapi.puppet.com` DNS records (as well as the legacy ` forge.puppetlabs.com` and `forgeapi.puppetlabs.com` records) to point to a new IPv4 address. This change is being made as part of ongoing work to improve the perfo

[Puppet Users] Facter 4.0.43

*Facter 4.0.43* *Fixed* - (FACT-2810) Fix dmi.board_asset_tag and dhcp #2125 - (FACT-2817) Only invalidate session cache on clear and reset. #2121 - (maint) Fix virtual_detector #2128

[Puppet Users] Puppet Platform GPG signing changes starting November 2, 2020, action may be required

Why This Change Puppet sets its package signing keys to expire on a set schedule for good security practices. Summary On November 2, 2020, Puppet Release Engineering will start signing Puppet Platform and Puppet Enterprise packages with an updated GPG key. This is an explanati

Re: [Puppet Users] refactor use of ensure_packages to install new versions of php packages

On 10/12/20 5:10 AM, jochen@gmail.com wrote: > Hi all, > > I posted a question on Stackoverflow before the weekend, but no > responses and not many views yet, unfortunately. So please forgive me > asking this again here. refactor ensure_packages to switch version of > installed packages https:

Re: [Puppet Users] refactor use of ensure_packages to install new versions of php packages

I don't know if it'll work, but you *might* be able to do something like this: $php_package_1 = 'php${php_version}-xml' #single quoted to prevent interpolation $install_versions.each | String $php_version | { $php_install_1 = "${php_package_1}" #double quoted to now interpolate ensure

Re: [Puppet Users] refactor use of ensure_packages to install new versions of php packages

I think you will get sort of „cannot redeclare“… otherwise I agree, it would work like you suggest. But with the solution you propose, I guess I will have one structure for the packages to be installed and another for the ones to be removed. But I want to manage only one list of packages… more

Re: [Puppet Users] refactor use of ensure_packages to install new versions of php packages

If you redeclare the list *outside* the .each block, you'll end up with the same list. Also if you redeclare it outside, against the $php_remove array, you'll get something weird. If you redeclare it *inside* the .each block, it'll be local to that block, get destroyed on the second run, and y

Re: [Puppet Users] refactor use of ensure_packages to install new versions of php packages

thx for the smart ;-) but when I redeclare the list, I end up keeping two lists of packages. The guy who I am, I will definitely fuck this up regularly… and that’s back to the root of my problem… I would like to somehow reuse the $myPackages structure with different values for $php_version. M

[Puppet Users] Re: refactor use of ensure_packages to install new versions of php packages

Seems pretty smart to me, tbh. The only problem is that $myPackages is constant, so already includes the "7.4" values from $php_version. You'll need to declare a new list (because you can't change variables) inside your .each block. $php_remove.each | String $php_str_remove | { $myRemove

[Puppet Users] refactor use of ensure_packages to install new versions of php packages

Hi all, I posted a question on Stackoverflow before the weekend, but no responses and not many views yet, unfortunately. So please forgive me asking this again here. refactor ensure_packages to switch version of installed packages https://stackoverflow.com/q/64284862/13088564?sem=2 I am succe