https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • b
    some modules contain only ruby code, some contain only manifests, some contain only tasks, etc. So we can’t really require any of those to be present.
  • b
    then I vote for the idea from @jhoblitt. we block eveything and work with an allowlist to ensure modules are as minimal as possible
  • b
    👍
  • j
    smaller tarballs seems like a win for everyone. If not in terms of bandwidth, module unpacking time.
  • b
    from someone who has to maintain over 50 environments with 200 modules each: yes please, lets ship modules with less files. I run into IO bottlenecks during deployments :D
    🙏 3
  • b
    and with that I am off to bed o/
  • b
    later!
  • j
    cya
  • j
    @binford2k I know the forge looks at 
    metadata.json
    does it allow multiple file extensions for README, CHANGELOG, REFERNECE, etc?
  • j
    @binford2k I know the forge looks at 
    metadata.json
    does it allow multiple file extensions for README, CHANGELOG, REFERNECE, etc?
  • b
    we actually experimented with shipping Relay workflows as Puppet modules in a workflow directory, because the Forge doesn’t care what’s in a module.
  • j
    Ya... I see all kinds of strange things running 
    ack
    in my control repo with modules cloned
  • b
    there’s a resolver… think it looks for downcased .md, .markdown, .mkd, .txt
  • b
    but I’d have to go check
  • j
    I have worked hard to get my production envs to < 125 puppet mods installed
  • j
    it will be nice to cleanout some of the junk being copied around
  • b
    truth
  • b
    and i really REALLY want to develop the concept of optional dependencies
  • b
    haven’t gotten there yet though
  • j
    optional deps are hard
  • b
    yep. My naive approach is that optional deps are listed but not resolved/installed by my puppetfile resolver. If you want them, you’d have to add them manually and resolve again.
  • b
    so many edge cases that we can’t agree on implementation though 😁
  • j
    I have yet to see a packaging system with optional deps that seem... well... usable. Cargo has optional deps but the constraint resolver must be insanely complicated.
  • b
    and some of them are only semi-optional. Like it might be a hard requirement if any of your nodes are a certain platform and unused otherwise.
  • j
    I would be absolute ecstatic if r10k would use a 
    librarian-puppet
    style .lock file and I could prune the puppetfile down to the direct dependencies of my control repo.
  • b
    my resolver gets close to that
  • j
    that sounds even more difficult because you would have to know in advance the specifics of every platform that will be in an env in the future... or trigger a redeploy if those specifics change
  • b
    ☝️ nearly impossible, imho
  • j
    If puppetserver could shoot out webhooks when the number of hosts / facts in an env change... or if it had a k8s style "wait" api...
  • j
    or I suppose you could have a set of rules for constructing "sub envs" per host that dynamically update when an agent phones home with its set of facts
1...130131132...648Latest