goodnews 🧑‍🏫 Bolt is about to start up in #CFD8Z9A4T

This message was deleted.

I got very specific puppet env.. e.g. ppl are using run stages here 😞 then I found a "limitation" in

apt

module docs which says the module cannot be split across run stages.. Does it mean if I have Apt::Source in one stage I cannot

require

it in another stage? Shall I put all packages together with Apt::Source into the same stage then?

I got very specific puppet env.. e.g. ppl are using run stages here 😞 then I found a "limitation" in

apt

module docs which says the module cannot be split across run stages.. Does it mean if I have Apt::Source in one stage I cannot

require

it in another stage? Shall I put all packages together with Apt::Source into the same stage then?

yep

(or reduce the amount of stage and eventually get rid of them)

I definitely would like to get rid of them.. somehow I was able to avoid stages always.. but here we have a lot of legacy and very specific decisions.. well, ty anyway!

need some help getting rid of them or telling people it's bad practice? 🙂

join us! 😄

well, sometimes they are useful, like configuring satellite client or chocolatey enterprise, just have to remember limitations

but mostly it should be possible to arrange things in proper order with relationship metaparams I guess.. what are cases when it's not enough?

ah, I guess something like 'install a gem and use it in the same run' maybe

I have 3 stages, but I think of them as 3 separate puppet runs

first stage is literally just ntp/resolver/ssl certificates that I know are required to be right before I can actually configure a system

I'd say it's ok if Puppet enforces you to split all those resources by different files/modules.. so one cannot just put everything into the same manifest and assign stages randomly..

I mean, it totally can to a large extent

I have a profile that generates the stages and calls a list of profile classes to load into the stages

but I am odd in that I version my profile submoduless each as their own modules

Consider a case where you need to configure say LDAP integration and do it before any user resource is created. It's much simpler to put it in a

setup

stage. Collectors are bad, you will get virtual resources released

This message was deleted.

if "good practices" is applicable here 😄

if "good practices" is applicable here 😄

This message was deleted.

Hey all. How would you pass class variables as parameters from node definitions? I'm trying the following but it keeps erroring on a line in site.pp that isn't even related. Using v6

what's the error?

This message was deleted.

Missing a colon in your notify

@Lumiere 100%! Thanks a bunch!

just as a note, if you can use code snippets in slack, it's 1000% easier to read them 😄