=== andrewbogott is now known as Guest6437
=== Daniel is now known as toolz
[11:51] <Deckard111> hi everyone
[11:51] <Deckard111> when I do : cloud-init query sys_info.uname
[11:52] <Deckard111> I get 
[11:52] <Deckard111> ti
[11:52] <Deckard111> [
[11:52] <Deckard111>  "Linux",
[11:52] <Deckard111>  "0.limesurvey.host",
[11:52] <Deckard111>  "5.4.0-77-generic",
[11:52] <Deckard111>  "#86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021",
[11:52] <Deckard111>  "x86_64",
[11:52] <Deckard111>  "x86_64"
[11:52] <Deckard111> ]
[11:52] <Deckard111> how would I access the 2nd string, only?
[11:52] <Deckard111> I need it in cloud-config
[12:31] <falcojr> uname -n?
[12:41] <Deckard111> found a way to read it and output it using jinja
[12:41] <Deckard111> {{ sys_info.uname[1] }}
[12:42] <Deckard111> however this key seems to change value at some point so i get back a different value
[12:42] <Deckard111> so I am using {{ ds.meta_data.local_hostname }}
[12:42] <Deckard111> which works
[12:43] <Deckard111> falcojr uname-n would only work in the command section but I need to use it in the debconf module
[13:09] <Deckard111> there is stil something fishy though
[13:41] <Deckard111> I have another question:
[13:42] <Deckard111> A cloud init config may sometimes include sensitive information. What is the best way to wipe all config data, once cloud-init is finished?
[13:45] <falcojr> the sensitive data gets stored in /run/cloud-init/instance-data-sensitive.json , but that file is only root readable and should get wiped on reboot
[13:45] <falcojr> and same with cloud-init query. If you're not running as root, it shouldn't return the sensitive data
[13:47] <Deckard111> hm.. I can find copies of it in /var/lib/cloud/instances/12954850/user-data.txt
[13:49] <Deckard111> is that provider-specific or also from cloud-init?
[13:50] <falcojr> there's no supported way to remove that data
[14:05] <Deckard111> Could I just do it as a last command before reboot? Or would I saw off the branch I am sitting on? Let's try ;)
[14:35] <Deckard111> ok, I can definitely say that cloud-init does not like that ;)