https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • v

    VoxBot

    11/21/2022, 5:55 PM
    big +1 to that
  • v

    VoxBot

    11/21/2022, 5:57 PM
    I wish Puppet itself had a built in default layout for the data directory - as long as you follow the convention, no hiera.yaml should be needed IMHO
  • v

    VoxBot

    11/21/2022, 5:59 PM
    in https://github.com/voxpupuli/beaker-hiera we do generate some layout too (though that's global, not for modules) and I wonder if that should follow the same conventions
  • j

    jhoblitt

    11/21/2022, 6:09 PM
    UGH
  • j

    jhoblitt

    11/21/2022, 6:09 PM
    some idiot just pushed 5.0.0 release prep onto the master branch for puppet-lldpd... https://github.com/voxpupuli/puppet-lldpd/commits/master
  • d

    Dr Bunsen Honeydew

    11/21/2022, 6:09 PM
    See the
    puppet-lldpd
    module at https://forge.puppet.com/puppet/lldpd?src=slack&channel=voxpupuli
  • j

    jhoblitt

    11/21/2022, 6:10 PM
    I'm not even if sure what the branch protection is... can I do a forced push on master to undo?
  • v

    VoxBot

    11/21/2022, 6:11 PM
    yes, but not sure why you need to
  • j

    jhoblitt

    11/21/2022, 6:11 PM
    yes I can...
  • j

    jhoblitt

    11/21/2022, 6:11 PM
    well there was no PR for the release
  • v

    VoxBot

    11/21/2022, 6:11 PM
    ah, yes
  • v

    VoxBot

    11/21/2022, 6:12 PM
    I wish our changelog generator skipped issues that had a PR attached
  • j

    jhoblitt

    11/21/2022, 6:13 PM
    wait, no I can't... can't force push to master
  • j

    jhoblitt

    11/21/2022, 6:13 PM
    well, I guess that release is done
  • j

    jhoblitt

    11/21/2022, 6:13 PM
    @ewoud could you eyeball this commit? https://github.com/voxpupuli/puppet-lldpd/commit/19b309fb3fe88ff82c1a0bf0cda63581985633f8
  • v

    VoxBot

    11/21/2022, 6:16 PM
    could you submit a PR for 5.0.0 that updates the changelog? I added some labels
    🙏 1
  • j

    jhoblitt

    11/21/2022, 6:18 PM
    https://github.com/voxpupuli/puppet-lldpd/pull/146
  • j

    jhoblitt

    11/21/2022, 6:18 PM
    https://github.com/voxpupuli/puppet-lldpd/pull/146
  • s

    Slackbot

    11/21/2022, 6:20 PM
    This message was deleted.
    j
    • 2
    • 2
  • a

    Alex Fisher

    11/21/2022, 6:20 PM
    I'm wondering how harmful it would or wouldn't be if we did want to vanish the 3 commits pushed directly to master.
  • j

    jhoblitt

    11/21/2022, 6:21 PM
    depends on how many clones were sync'd after the push
  • s

    Slackbot

    11/21/2022, 6:21 PM
    This message was deleted.
    j
    • 2
    • 1
  • j

    jhoblitt

    11/21/2022, 6:22 PM
    if we changed the rake target to open a PR for the -rc we could block direct pushes to master completely
  • v

    VoxBot

    11/21/2022, 6:22 PM
    well, the message was "update CHANGELOG.md for 5.0.0 release", not actually "release 5.0.0"
  • a

    Alex Fisher

    11/21/2022, 6:22 PM
    I think the release task itself needs to.
  • j

    jhoblitt

    11/21/2022, 6:22 PM
    because it commits on metadata.json and pushes it... there's no reason that has to be pushed to master
  • v

    VoxBot

    11/21/2022, 6:24 PM
    technically what you can also do is submit the bump to rc0 in the original PR and "just" make sure the tag points to the correct commit
  • j

    jhoblitt

    11/21/2022, 6:25 PM
    what could possibly go wrong 😉
  • j

    jhoblitt

    11/21/2022, 6:25 PM
    https://github.com/voxpupuli/puppet-lldpd/actions/runs/3517080364 let us never speak of this incident again...
  • a

    Alex Fisher

    11/21/2022, 6:27 PM
    No problem. That looks like it's a least the correct commit. (although I would have probably gone with ewoud's suggestion over commit message)
1...193194195...648Latest