https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • v
  • v
    those stupid slack threads...
  • v
    by externalizing most of the config to a gem it's easy to update a base config
  • v
    ewoud: the message comes from a thread, but I cant find' that in slack :D
  • v
    and it's pretty trivial to not template it at all, but still benefit from the defaults
  • b
    @rusty @CVQuesty ^
  • v
    so to clarify: I have issues with both PDK itself, and pdk-templates, but I'd start with working on pdk-templates and voxpupuli/modulesync_config alignment
  • v
    I'd say that for persona 1) removing as much synced code as possible (like we did with our modulesync_config) is a huge win
  • v
    and for persona 2) it's also a win
  • v
    nods
  • v
    so that's where I started
  • v
    syncing files is an antipattern and that should be reduced. by doing that vox pupuli and puppet setup come automatically closer
  • v
    exactly
  • y
    nods here too
  • c
    @bastelfreak yeah agree
  • y
    where can I look for a modern enough Rakefile to sync the beaker-docker’s with?
  • c
    Scaffolding is the way I want to go
  • v
    https://github.com/voxpupuli/beaker/pull/1784 victory! at least with just Ruby 3.2 it's green
  • c
    but include guard rails to keep people within known bounds for compatibility
  • v
    now to run on all Ruby versions and see what else breaks
  • b
    @Yury Bushmelev https://github.com/voxpupuli/puppet-grafana/blob/master/Rakefile that's our latest Rakefile
    🙇🏻 1
  • b
    @Yury Bushmelev https://github.com/voxpupuli/puppet-grafana/blob/master/Rakefile that's our latest Rakefile
  • v
    ewoud++
  • d
    ewoud leveled up! (Karma: 3)
  • v
    Craig: if you want to go that route, perhaps make sure the Ruby tooling can actually read a config file?
    👍 1
  • b
    @Yury Bushmelev oh you mean for gems? one sec
  • v
    I mean, perhaps not for everything it'll work, but for spec_helper.rb if there are known toggles then perhaps reading a config file is better
  • y
    @bastelfreak I’d say we should have the same Rakefile across the beaker plugins (at least)
  • y
    @bastelfreak I’d say we should have the same Rakefile across the beaker plugins (at least)
  • b
    yeah that's my longterm plan. I think for now the beaker-docker Rakefile can stay as it it in master. It has the tasks for rubocop, changelog generator and unit tests
1...371372373...648Latest