https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • y
    how can I tell the Beaker to deploy the repository as an environment? It deploys it as a module under $modulepath..
  • y
    not sure if Beaker is designed for this though..
  • y
    my idea is to use Beaker for control_repo acceptance testing
  • b
    good question, I am not sure if thats configureable
  • b
    maybe puppet-beaker does that
  • y
    Copy code
    copy_module_to(hosts, module_name: 'production', target_module_path: '/etc/puppetlabs/code/environments')
  • y
    now I should find and remove all the hacks and workarounds I tried before 😄
  • v
    in vp-acceptance we have a different mechanism as well: https://github.com/voxpupuli/voxpupuli-acceptance#fixtures
  • v
  • y
    yes, but what I need is to deploy the whole repo as an environment
  • v
    I think you may need to do some work for that, but all the code is there in voxpupuli-acceptance
  • y
    I achieved it with the command above.. just copy the current dir to the production env 🙂
  • y
    JFYI, here is some Frankenstein monster I did on the weekend: https://github.com/jay7x/puppetbolt-control_repo. Feel free to comment and reuse 🙂
    panda eat 1
    looking 3
  • y
    JFYI, here is some Frankenstein monster I did on the weekend: https://github.com/jay7x/puppetbolt-control_repo. Feel free to comment and reuse 🙂
  • m
    Is there anyone that could help https://github.com/voxpupuli/puppet-windows_env/issues/12 - the develop branch I believe has the fixes but seems abandoned. It needs some rebasing/factoring. Posted in #windows
  • m
    message has been deleted
  • v
    commented in #windows
  • v
    https://github.com/mmckinst/puppet-lint-legacy_facts-check/pull/40#issuecomment-1399867401 at least some progress, though he lists Apple as his employer and they're known to not allow open source by default :(
  • v
    something, something, europe ;)
  • v
    if it ends up in our org it's probably the best outcome
  • v
    ewoud: the new puppetlabs_spec_helper release is out, as v5.0.0
  • v
    bastelfreak: nice
  • v
    hmm, interesting choice: puppet version at least 6.0 and Ruby at least 2.7, but Puppet 6 doesn't run on Ruby 2.7
  • v
  • v
    https://github.com/puppetlabs/puppetlabs_spec_helper/issues/372 that'll be an issue in adoption of puppetlabs_spec_helper 5.0.0
  • v
    lol
  • v
    meh
  • v
    I think we packaged Puppet 6 on Ruby 2.7 for Arch Linux and that worked, but it would help if the lower ruby version alings with what's in the Puppet AIO package
  • v
    exactly
  • a
    ewoud: puppet-lint is a bit of a mess really, isn't it?
1...252253254...648Latest