[00:32] <minimal> blackboxsw: ah ok, I was considering patching the Alpine package if it affected all renderers but now I know I'll just wait for 22.3.1
[15:42] <jbg> how can i completely disable the processing/merging of vendor data in cloud-init?
[15:42] <jbg> the docs say "Vendordata can be disabled by the user" but don't seem to mention *how* anywhere
[15:45] <blackboxsw> jbg: It's `vendor_data: false` in #cloud-config user-data provided during system launch I believe https://cloudinit.readthedocs.io/en/latest/topics/modules.html#scripts-vendor
[15:46] <blackboxsw> I'm double checking to be sure
[15:48] <blackboxsw> sorry I mean the folowing `vendor_data: {enabled: false}`
[15:50] <jbg> hm okay, does this mean if i am overriding the modules that run and don't include scripts-vendor, it should have the same effect?
[15:51] <jbg> because if so then the problem i thought was caused by vendor-data must be caused by something else, heh
[15:52] <jbg> i'll try it out anyway and see
[20:03] <beantaxi> Hello all ... what's the best way to parameterize my otherwise standard cloud-init.cfg with values like repo name, etc? I'm not seeing an idiomatic way to do it in instance data or other mechanism, so I wonder if I am expected to do that myself via a template engine, sed, etc. Thanks!
=== jbg_ is now known as jbg
=== madhens_ is now known as madhens
=== dch_ is now known as dch