PR submitted https://github.com/puppetlabs/puppetlabs-apache/pull/2307

This message was deleted.

Is the key you're looking up

foo.bar.baz.quix

? and it is a hash with key

keytab_base64

? Does the below work?

aliased_key: "%{alias(\"foo.bar.baz.quix\".keytab_base64)}"

Passing the variable to the function as a parameter is indeed probably best. You can get access to puppet variables in a function, though, via: https://puppet.com/docs/puppet/7/functions_ruby_implementation.html#functions_ruby_implementation-accessing-variables I don't know if that works with the old v3 function API. In general, you may have an easier time doing the upgrade bit by bit rather than all at once. I recall that upgrading from puppet 3 to 4 was much more difficult than future upgrades. I recommend, in general, to: 1. Enable the future parser and make your codebase work with that. https://github.com/puppetlabs/docs-archive/blob/main/puppet/3.8/experiments_future.markdown 2. Upgrade to puppet 4 and make your codebase work with that. 3. Upgrade to puppet 5, etc.

This message was deleted.

Hi team, is it possible to configure

package

to only upgrade a package if it is already installed? I am porting code from Ansible and we set https://docs.ansible.com/ansible/latest/collections/ansible/builtin/apt_module.html#parameter-only_upgradeto to

true

and supply a list of packages. So the playbook upgrades packages on VMs that already exist and on others it does not do anything. Can I mimic that behavior with puppet?

can we not change this

Optional[Variant[Stdlib::Absolutepath, Boolean[False]]] $vhost_enable_dir = $apache::params::vhost_enable_dir,

to

Boolean

and set the default to

true

then fix the code path so that it actually behaves like a toggle?

can you link me the code?

goodnews 🧑‍🏫Puppet Forge is about to start up in #CFD8Z9A4T

Hello, It's not possible to doing something like this on my spec helper ?

# 'spec_overrides' from sync.yml will appear below this line
RSpec.configure do |c|
  c.before :each do
    Puppet::Functions.create_function(:'synapps::metadatas') do
      dispatch :metadatas do
        param 'String', :asset_id
      end

      def metadatas(asset_id)
        {}
      end
    end
  end
end

This is a custom function using an external api

This message was deleted.

Even if you get to call the function agent side there isnt much you can do to modify the catalog being applied.

This message was deleted.

This message was deleted.

Not sure I understand the question

This message was deleted.

indeed 🧑‍🏫PE Console is about to start up in #CFD8Z9A4T

hi all, Puppetserver 7.9.0 Puppet-Agent 7.18.0 on Windows Server 2019 Error in Windows eventlogs:

Failed to determine runinterval, defaulting to 1800 seconds

In C\ProgramData\PuppetLabs\puppet\etc\puppet.conf

runinterval=10m

Does anyone know why ? thanks in advance

This message was deleted.

Maybe wrong puppet.conf section

thanks for your answer @fe80 I did like you said:

PS C:\Users\admin> puppet config print runinterval
600
PS C:\Users\admin> puppet config set --section main runinterval 10m
PS C:\Users\admin> puppet config print runinterval
600

ANd when I restart the service in Services I still see the error in Windows Event-logs

Failed to determine loglevel, defaulting to notice

Failed to determine runinterval, defaulting to 1800 seconds

@fe80 thats right i look in

C:/ProgramData/PuppetLabs/puppet/etc/puppet.conf

Thats what make me crazy! I dont know why!

@fe80 I try also this:

sc stop puppet && sc start puppet --logtofile  --debug --trace

@fe80 I try also this to see more informations but nothing news:

sc stop puppet && sc start puppet --logtofile  --debug --trace

@fe80 I try also this to see more informations but nothing new:

sc stop puppet && sc start puppet --logtofile  --debug --trace

This message was deleted.

OK it is Friday morning and I think I am blind because I fail to see why facter will not load a fact under a dir:

root@puppetserver-003:~# facter --debug --verbose --trace --custom-dir=./my_facts foo_bar
[2022-09-09 08:49:08.415095 ] INFO Facter - executed with command line: --debug --verbose --trace --custom-dir=./my_facts foo_bar

root@puppetserver-003:~# ls ./my_facts
foo_bar.rb
root@puppetserver-003:~# cat ./my_facts/foo_bar.rb
# foo_bar.rb
Facter.add('foo_bar') do
  setcode do
    Facter::Core::Execution.execute('/bin/uname --hardware-platform')
  end
end

strace confirms that

strace -e trace=openat facter --debug --verbose --trace --custom-dir=./my_facts foo_bar 2>&1 |grep foo_bar

This message was deleted.