for the sake of sharing, a colleague of mine created a function to manage the firewall, similarly to how you would do on Google/AWS with terraform. It relies on PuppetDB, Voxpupuli/ipset and Puppetlabs/firewall. You can choose either a "public" zone and a trust zone (this is the trust, where you specify your sources through IPSET). How do you like it? 🙂

for the sake of sharing, a colleague of mine created few functions to manage the firewall, similarly to how you would do on Google/AWS with terraform. It relies on PuppetDB, Voxpupuli/ipset and Puppetlabs/firewall. You can choose either a "public" zone and a trust zone (this is the trust, where you specify your sources through IPSET). How do you like it? 🙂

for the sake of sharing, a colleague of mine created a function to manage the firewall, similarly to how you would do on Google/AWS with terraform. It relies on PuppetDB, Voxpupuli/ipset and Puppetlabs/firewall. You can choose either a "public" zone and a trust zone (this is the trust, where you specify your sources through IPSET). How do you like it? 🙂

voxpupuli/ipset ❤️

This message was deleted.

check out https://forge.puppet.com/modules/puppet/r10k#webhook-support

Thanks! I've found a bunch of references to using gitlab to trigger r10k but had not found and recent step by step guides, just something Super old

the successor of that webhook is https://github.com/voxpupuli/webhook-go

the successor of that webhook is https://github.com/voxpupuli/webhook-go

ah yeah there's the Go one now as well

I’ve seen this pattern (like in the Telegraf module) where roles look like they could be fully defined in hieradata. I’m more familiar with the site-roles-profiles defined within a control repo. I have questions that maybe someone can point me to links to get answers for: • How do you test around hiera-based role definitions? • How might you bring in hiera definitions into the hierarchy if you wanted the roles and profiles to exist in their own repos?

I’m in the middle of taking an over-blown ENC and converting it to something a bit more sane and rather than take it to a 5+ year-old pattern, it’d be nice to be even more current.

Non-PE environment for me.

We migrated from site/role to corp:role:, makes it a standard module

the more you know 🧑‍🏫PE Console is about to start up in #CFD8Z9A4T

@Joel Wilson a role in many environments I manage is a yaml file with a classes array. you can test it easily with rpsec-puppet to check if the catalog compiles and contains all related profiles in the correct order, or spin up a beaker instance and check if the role applies. this can live in a control-repo or as module-data in a module

I have to imagine that if I have a

data/role

directory in my

roles

module and the

roles

module’s

hiera.yaml

correctly explained how to map a

$::role

fact to files in that directory, I could just put in YAML like the following and it would appropriately bring in the mix of classes from the rest of the modulepath:

---
profiles::nginx
profiles::network_setup
telegraf::global_tags:
  etc:

```- took a hit! Ouch. (Karma: -78)

yep

```- took a hit! Ouch. (Karma: -79)

How do you map an rspec file to an appropriate role in the data dir?

I made the doctor unhappy

you loop over a list of roles and mock each role as fact, so hiera will use the yaml

Not sure I get the distinction between our two YAML examples. One of your groups is `include`s and one is class declaration style?

classes is an array

and in the site.pp I do a lookup on $classea, loop on the result and include everything

there is nothing special about this word, just a convention

Seems easier

contain lookup('classes', Array[String], 'unique', [])