https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • w
    Not a monolithic clone of a server that is ~2 years old
  • b
    if prod is already managed with Puppet, you could spin up test instances with the same code on demand
  • w
    Unfortunately puppet is a new introduction to our environment.
  • b
    or keep a permanent dev instance running and ensure with puppet that prod is insync
  • w
    Even git and provisioning scripts would be preferential
  • b
    perfect first project for Puppet!
    💯 1
  • l
    honestly, the entire paradigm is backward
  • l
    build a dev, patch and maintain it ensure things work in it
  • l
    then deploy that to production
  • w
    Yeah, the current paradigm is clone prod virtual machine to dev, test thing then repeat steps on prod
  • w
    Yeah, the current paradigm is clone prod to dev, test thing then repeat steps on prod
  • w
    Yeah, the current paradigm is clone prod virtual machine to dev, test thing then repeat steps on prod
  • w
    Usually replacing test/dev vms that already exist but have config drift issues
  • b
    that sounds... not so nice
  • y
    Testing in production—except it is now (dev|test|staging). 😆
  • s
    This message was deleted.
    b
    n
    c
    • 4
    • 8
  • n
    Hi Everyone, I am still getting to grips with PQL. Is it possible to get to details out of a puppet qpl query: Where is my query: 
    inventory[certname] { facts.os.name = "RedHat" }
    I would like to get the cert name and the OS Version e.g. RedHat 7
  • s
    This message was deleted.
    j
    d
    • 3
    • 4
  • a
    @reidmv Hi! I've been trying out your certificate module. https://github.com/reidmv/puppet-module-puppet_certificate Looks really useful in automating agent cert renewals.
  • a
    @reidmv Hi! I've been trying out your certificate module. https://github.com/reidmv/puppet-module-puppet_certificate Looks really useful in automating agent cert renewals.
  • a
    One thing I noticed is that the certificate that the type claims to download is apparently not being stored anywhere. If I do a second run, then puppet requests it again. It's not ideal though as I intend for my policy to use a secret in the csr that will only last 10 or so minutes.
  • b
    did you see that on puppet 6 or 7?
  • a
    6.
  • a
    I can see that for 7 it might need some fixes too.
  • a
    I'm implementing https://dev.to/camptocamp-ops/automatic-renewal-of-puppet-certificates-28pm and trying to do "Another idea is to generate a composite secret on the Puppet master by mixing the psk with the certname" as part of that.
  • r
    @Alex Fisher I think the last time I used that puppet_certificate type was in a much older version of Puppet. I am not surprised to hear that it (sounds like it) needs some TLC for Puppet 6/7. 🙂
  • a
    ok. There was https://github.com/reidmv/puppet-module-puppet_certificate/pull/7 but I guess it might have been incomplete???
  • a
    ok. There was https://github.com/reidmv/puppet-module-puppet_certificate/pull/7 but I guess it might have been incomplete???
  • a
    Reading this thread, looks like there might be a fork I could test out. https://github.com/reidmv/puppet-module-puppet_certificate/issues/10#issuecomment-1002141468
    👍 1
  • a
    Reading this thread, looks like there might be a fork I could test out. https://github.com/reidmv/puppet-module-puppet_certificate/issues/10#issuecomment-1002141468
1...212213214...428Latest