https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • r
    If anyone wants to put in a pull-request to mine I'm more than happy to review/merge/forge-publish, but I don't spend a lot of time on it myself these days so I don't realistically see myself putting together a fix.
  • a
    I'm also in the unfortunate position of also wanting it to work on Puppet 3 on Solaris, so umm... I might have to create my own fork until I can finally get those agents upgraded! šŸ˜ž
  • r
    Or if anyone is passionate about it and wants contributor access that's totally on the table too. Heck, I'd be happy to hand it off to Vox Pupuli, if it didn't require a lot of time from me to package it up for that.
  • a
    ok. I'll test what's there with Puppet 6 (and 3!!) and create a PR if I think it looks good. Seems like there's some other community interest too.
    šŸ”„ 1
    rockon 1
    šŸ‘ 1
  • a
    @bastelfreak Are you interested in it too?
  • b
    for Puppet 6/7, yes
  • s
    This message was deleted.
    r
    b
    a
    • 4
    • 16
  • d
    businessparrot šŸ§‘ā€šŸ«Puppet Core Team is about to start up in #CFD8Z9A4T
  • b
    @Alex Fisher Count me in as interested as well
    ā¤ļø 1
  • c
    Maybe Iā€™m late to the party, but where did stahnma-epel go? Thereā€™s a couple of REALLY IMPORTANT Amazon modules that rely on it, and it doesnā€™t even have a deprecation anywhere that I can find, and itā€™s not in Michaelā€™s GitHub
  • d
  • c
    I appar to have misspelled
  • c
    šŸ˜„
  • c
    Still deprecated, though
  • c
    bryana-ec2tagfacts and jdowning-awscli both require it, though. And they havenā€™t updated.
  • d
  • b
    we adopted the epel module ages ago šŸ™‚ (but I think it should be deprecated)
  • s
    This message was deleted.
    l
    b
    • 3
    • 5
  • l
    message has been deleted
  • b
    hey hey hey, the world is waking up again! Who's up for speaking at cfgmgmtcamp this February? https://cfgmgmtcamp.eu/ghent2023/
  • s
    This message was deleted.
    j
    l
    +2
    • 5
    • 19
  • d
    beaker šŸ§‘ā€šŸ« Bolt is about to start up in #CFD8Z9A4T
  • s
    This message was deleted.
    j
    c
    h
    • 4
    • 5
  • w
    I'm trying to get eyaml within a module working correctly, The value isn't currently encrypted.. I have this in my module specific hiera data
    Copy code
    - name: "secret data"
      path: "secrets.eyaml"
      options:
        pkcs7_private_key: /etc/puppetlabs/puppet/keys/private_key.pkcs7.pem 
        pkcs7_public_key: /etc/puppetlabs/puppet/keys/public_key.pkcs7.pem
    However, when I run a puppet agent -t I get this,
    Copy code
    Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, (/etc/puppetlabs/code/environments/test/modules/account_svcansiblelocal/hiera.yaml): expected <block end>, but found '<block mapping start>' while parsing a block mapping at line 23 column 7 (file: /etc/puppetlabs/code/environments/test/manifests/site.pp, line: 10, column: 3) on node <http://vmpuppetmaster01.britanniahome.net|vmpuppetmaster01.britanniahome.net>
  • w
    The keys are owned by "puppet" and chmod 600
  • w
    Copy code
    etc/puppetlabs/code/environments/test/modules/account_svcansiblelocal/data$ sudo puppetserver gem list | grep eyaml
hiera-eyaml (3.3.0)
  • n
    Is that the only eyaml config options in your hiera.yaml? Itā€™s missing the 
    lookup_key
    option.
  • n
    See the example hiera.yaml config in https://github.com/voxpupuli/hiera-eyaml#with-hiera-5
  • w
    yea
  • n
    That error means your 
    hiera.yaml
    is corrupt. Itā€™s not a problem with the keys.
1...213214215...428Latest