This message was deleted.

Hello Everyone, I want to make changes to the

/_etc/ssh/sshd_config_

file, with below lines: • AllowTcpForwarding yes • MaxStartups 100 And, it requires for only 2 servers

Hello Everyone, I want to make changes to the

/_etc/ssh/sshd_config_

file, with below lines: • AllowTcpForwarding yes • MaxStartups 100 And, it requires for only 3 puppet agent systems

This message was deleted.

See the

herculesteam-augeasproviders_ssh

module at https://forge.puppet.com/herculesteam/augeasproviders_ssh?src=slack&channel=puppet

This message was deleted.

When using eyaml can I just combine eyaml and yaml paths together into a single layer? Does this have a performance impact since it would be using eyaml as the lookup method even though only a few keys are encrypted?

Yes, you can just use the

eyaml

backend and mix both yaml and eyaml in a single layer. That’s what I prefer to do, because it simplifies things (IMO).

If there is a performance impact, I haven’t ever noticed it.

If there is a performance impact, I haven’t ever noticed it.

Marginally (insignificantly) slower I would expect

Why does the former work and not the latter?

# Silly, poor use
  class { "puppet": * => lookup('puppet') }
  class { "foreman": * => lookup('foreman') }

  # proper...
  include puppet
  include foreman

Can you clarify what you mean by work? Those are two completely different things.

the former literally search for one key only

not puppet::argument

not puppet::argument

@vchepkov oh, that’s probably it.

Automatic parameter works by prefixing the key names in hiera with the class name. Not by puttting the class parameters in a key named after the class. e.g. You want your Hiera data to look like this:

puppet::param_1: "foo"
puppet::param_2: "bar"
forman::param_1: "hi"
forman::param_2: "earth"

Not like this:

puppet:
  param_1: "foo"
  param_2: "bar"

@natemccurdy yessir. 🤦‍♂️

I used my foreman-answers.yaml as a starting point and it doesn’t have the prefixing.

Thanks @natemccurdy and @vchepkov

having a strange issue... I have created a script to generate self signed certs with OpenSSL. Using

puppet agent -t --debug

I can see that the powershell command being called is

powershell -ExecutionPolicy ByPass -File C:\Installs\SelfSignedCertScript\Create-SelfSignedCert.ps1 -OutputPath "C:\Program Files\SonarQube\Certificates" -Domain "sonarqube.company.local"

When I run that command in a

cmd

shell, I get the certificates that I expect. When it runs in Puppet, the certificates are not created. Attached is the output I'm getting from the

cmd

window. I don't see any obvious reason why the script would fail to create the certificate when run by puppet

the first lines are creation of the private key, which never materializes in the output folder when run by puppet. The "signature ok" line is the command to generate the CSR, and the the subject line is the command to create the cert from the key and CSR

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

I figured out how to suppress all output, and my certificates are still not being created

What does your Puppet code look like that’s running that script?

(note that Puppet running an

exec

is usually very different in context than you running the script by hand. It’ll running as an administrator, for one thing, not your user.)

This message was deleted.

(not enough screen real estate on my laptop)