https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • b
    if you want to keep maintaining it, you can do that in the vox pupuli namespace and benefit from our tooling
    👍 1
  • v
    then I'll start the migration
  • b
    perfect
  • b
    @voxel should cyberkov keep access?
  • v
    yes please
  • b
    okay, will invite him
  • v
    Thank you
  • b
    done
  • b
    I also configured the secrets
  • v
    Great Thanks!
  • v
    Am I right puppet 6 and 8 Tests are currently not working?
  • c
    Thanks fir the invite @bastelfreak. I am in this channel as well 🙂
  • b
    ah hi! :D
  • a
    @bastelfreak Morning!
  • v
    RUN!
  • v
    eh, hi Alex!
  • a
    I'm planning on squashing and merging https://github.com/voxpupuli/puppet-puppet_certificate/pull/12 despite any test failures so that we can finally get a release out (with functionality for old Puppet releases). After that, we can drop old code if people really want to and do another major release.
  • b
    @Alex Fisher sounds good to me
  • a
    Meanwhile... does anyone have any opinions on nested function namespaces? For example, if I had a few related functions to do with certificates that I wanted to submit to either stdlib or extlib, what would you think about putting them all under eg. 
    stdlib::x509::
    ?
  • a
    stdlib::x509::validate_chain
    stdlib::x509::issuer
    stdlib::x509::subject
    etc.
  • a
    and 
    stdlib::x509::validate_private_key
  • b
    I like it
  • b
    and if stdlib doesn't want them, maybe our openssl module is the right place
  • a
    yeah, maybe. But lots of people already have their own 
    certificate
    module etc so using one of the standard libraries would avoid a name clash.
  • a
    @bastelfreak Trying to relicense things again? 😉
  • b
    which repo is that?
  • a
  • b
    I usually dont relicense :D
  • a
    copy and paste error I guess.
  • b
    ah just a copy and paste error
1...477478479...642Latest