[16:36] <hetii> Hello :)
[16:36] <hetii> I have couple question about cloud-init/config files.
[16:39] <hetii> First I use terraform template_cloudinit_config data object where I can provide multiple parts that are encoded to multipart mime object. Each part of this message container header for eg for filename like:
[16:39] <hetii> Content-Disposition: attachment; filename="cloudinit.yaml"
[16:39] <hetii> how this file or content is then reference in boot process?
[16:40] <hetii> for eg can I embed https certificate for nginx daemon and use that mime object as a source data?
[16:42] <hetii> the second question is about cloud init portability. So by default my openstack provider have ubuntu images that support cloud-init, but do I assume correctly that cloud-init from ubuntu have different subset of stuff then for eg. cloudinit for rancheros?
[18:16] <meena> hetii: wha
[18:16] <hetii> ?
[18:16] <meena> … typing in phones is hard
[18:16] <hetii> ok
[18:17] <meena> anyway, given that rancher os advertises itself as being configurable via cloud-init, i don't think you have to worry
[18:18] <hetii> Well I need to know basic thing regarding boot process and paths handling in mime mix of cloud-init
[18:19] <meena> that's probably one of the areas i cannot help :( i try to avoid needing multiple files
[18:20] <hetii> ok, dont worry I will figureout
[18:21] <meena> extrapolating from my cloud provider, your nginx cert will end up in /var/lib/cloud-init/instance/
[18:40] <hetii> ok thx will check it also:)
[20:12] <meena> i just installed https://pypi.org/project/pipx/ — and saw Creator/Maintainer Chad Smith. and it's not blackboxsw. Apparently there's more than one.?!
[20:20] <hetii> re