what would "defaults" mean? the contents of the last path in the hiera.yaml?

we have an open issue for that since years :)

You'd have to essentially have puppet-strings implement the ability to parse both the hiera.yaml file and use that to parse the defaults from the module data

genebean[m]: https://github.com/puppetlabs/puppet-strings/issues/250 maybe you know people at puppez that you can ping about it

Thanks. and https://github.com/voxpupuli/puppet-grafana/pull/282 is what I've actually been working on.

Also my understanding is that

Sensitive

resource parameters are stripped from the catalog when it is written to puppetdb

I just moved https://github.com/voxpupuli/genebean-falco to the vox namespace - may I get some rights back on it please? Also, will an admin add the collaborators team to the module’s Collaborators & Teams ‘Teams’ list with Write permissions and add forge secrets

I, or an admin, needs to rename it to

puppet-falco

instead of

genebean-falco

too

This message was deleted.

@ramindk has left the channel

If anyone is around, https://github.com/voxpupuli/puppet-falco/pull/3 is ready for merge. Once it is in I am going to start a release PR for the 1.0.0 release which will be the first Vox release.

can I get a review for https://github.com/voxpupuli/voxpupuli-test/pull/79

.

bastelfreak: assuming something isn’t already in progress, where would be the right place to start proposing an updated release workflow that supports branch protection rules?

https://github.com/voxpupuli/voxpupuli-release/pull/19/files check that for the ruby code that does the release. ewoud started to update it.

https://github.com/voxpupuli/gha-puppet/blob/v1/.github/workflows/release.yml and that's the release workflow we use in all modules

afisher: do you want to review some of my puppet-catalog-diff PRs?

Thanks bastelfreak - I will take a look at those.

I can't remember, does Vox have tooling to set all the labels on a repo to a standardized set?

kinda yesno :D

lol

so previously there was a nodejs script that did this but that wa made by the devil and you needed to sacrifice 3 kittens. Then we startet with vox-pupuli-tasks, our rails app, that can do this. But that's currently in maintenance mode

we basically needs backwards-incompatible, modulesync, skip-changelog. bug should already exist

for company stuff, I think https://github.com/puppetlabs/community_management is still what is used to standardize labels... maybe there is something that can be ported from there to a rake task that is included by default if modulesync has been run. FWIW, the team I was on until recently put it to use like so:

```

```

bundle exec ruby labels.rb -n ploperations -r '^ploperations-' -f -d

one other question: do version tags include the v at the beginning or are they just the numbers and dots?

usually with a v

I think puppet-blacksmith enforces that