@tvaughan mind taking another look at https://github.com/voxpupuli/beaker-google/pull/17 when you get a few minutes?

ewoud: Morning!

morning

@binford2k As discussed in yesterday's sync, https://github.com/voxpupuli/webhook-go/issues/58

@binford2k As discussed in yesterday's sync, https://github.com/voxpupuli/webhook-go/issues/58

I dunno how useful the python snippet will be. Maybe it shows what correct queuing could look like??

It also shows one way of optimising the case where there have been multiple pushes to the same environment.

envs

is a

set

and the environments to be deployed are all read off the queue with duplicates discarded.

afisher: couldn't help myself and suggested an alternative based on your code

I'll just leave this here: https://twitter.com/Quasilocal/status/1569333921027858432

lol

ewoud: now if only we could find someone who could translate that to go! :)

afisher: or keep it pure python? extend it by calling programs if you want something chatops?

This message was deleted.

personally that's what I'd do, but I can't speak for others

mostly because I don't know go and rewriting it in Python is easier for me than to learn go

I mean, essentially it comes down to how complicated these 2 methods would be: https://gist.github.com/ekohl/92202f46501f80bed0ed5e1bb5923174#file-puppetcode-L40-L45

#198 (MAINT) Refactoring OSs based on puppet agent docs Pull request opened by jordanbreenpuppet Prior to this commit the metadata.json file for this module listed OSs that are not supported by puppet agent as supported. This commit aims to refactor the metadata.json file to only list OSs that are supported by puppet agent. This included the removal of CentOS 8 and Windows 2008 R2. The list of supported OSs can be found here: https://puppet.com/docs/pe/2021.7/supported_operating_systems.html puppetlabs/puppetlabs-facter_task GitHub Actions: Windows-2022, puppet7-nightly GitHub Actions: Windows-2022, puppet6-nightly GitHub Actions: Windows-2019, puppet7-nightly GitHub Actions: Windows-2019, puppet6-nightly GitHub Actions: Windows-2016, puppet7-nightly GitHub Actions: Windows-2016, puppet6-nightly GitHub Actions: Windows-2012 R2, puppet7-nightly GitHub Actions: Windows-2012 R2, puppet6-nightly GitHub Actions: Ubuntu-18.04, puppet6-nightly GitHub Actions: Rocky-8, puppet7-nightly GitHub Actions: RedHat-9, puppet7-nightly GitHub Actions: RedHat-9, puppet6-nightly GitHub Actions: RedHat-8, puppet7-nightly GitHub Actions: RedHat-8, puppet6-nightly GitHub Actions: RedHat-7, puppet7-nightly GitHub Actions: RedHat-7, puppet6-nightly GitHub Actions: Debian-11, puppet7-nightly ✅ 13 other checks have passed 13/30 successful checks

I think that the entire point of webhook-go is for people that don't want to drag in a complete dynamic language environment. If people are OK with that,

r10k::webhook

already has you covered

I am actually still using

r10k:webhook

but I am considering stuffing the entire thing into a docker container

This message was deleted.

It is unfortunate that https://github.com/puppetlabs-toy-chest/puppetlabs-image_build didn't take off

Related to webhook. I use smee as a queue for webhooks and smee passes the payloads on to

r10k::webhook

. https://forge.puppet.com/modules/lsst/smee

I am considering turning that into a docker container too

Who needs copilot when we have @ewoud?

This message was deleted.

See the

puppetlabs-image_build

module at https://forge.puppet.com/puppetlabs/image_build?src=slack&channel=voxpupuli

I'd say skopeo might be better because it should be able to squash layers directly iirc.. no need to run a container

Does voxpupuli consider debian 8 supported or dead?

dead

like debian 9