[16:36] <mayak> Hi all. Quick question, is it possible to modify the "cloud-init:" shell prompt, while the setup is running?
[17:00] <minimal> mayak: what shell? cloud-init does not provide a shell. Do you mean the console (or logfile) output of cloud-init?
[17:06] <blackboxsw> falcojr: holmanb base schema JSON for user-data merged now https://github.com/canonical/cloud-init/pull/1175
[17:07] <blackboxsw> so we can start chunking out all config module schema definitions now
[17:07] <falcojr> sounds good!
[17:19] <mayak> minimal: Oh yes, correct - I meant to say the console (or logfile) of cloud-init. In my case the output looks as follows (I am misusing the Ubuntu Live System in this case): https://abload.de/img/cloud-initugkar.png
[17:21] <mayak> If possible, I would like to remove the "prompt" part: [  48.0000] cloud-init [3387]:
[17:34] <blackboxsw> I believe that "prompt" is the name of the cloud-init process and the PID on your system. I believe that is standard rsyslog template format of the system you are on, not necessarily cloud-init related.  You might be able to tweak rsyslog templates to make some of that formatted output change. Admitedly I haven't done that before  and was googling things like https://www.rsyslog.com/doc/master/_downloads/rsyslog-example.conf
[17:36] <mayak> minimal Somehow I got disconnected from IRC in case you wrote me a reply. Sorry.
[17:38] <blackboxsw> mayak: I believe that "prompt" is the name of the cloud-init process and the PID on your system. I believe that is standard rsyslog template format of the system you are on, not necessarily cloud-init related.  You might be able to tweak rsyslog templates to make some of that formatted output change. Admitedly I haven't done that before  and was googling things like 
[17:38] <blackboxsw> https://www.rsyslog.com/doc/master/_downloads/rsyslog-example.conf
[17:38] <blackboxsw> though I admit that's not a very helpful response.
[17:39] <blackboxsw> https://rsyslog.readthedocs.io/en/latest/configuration/templates.html is better
[17:40] <mayak> Thank you very much, I will look through the links and let you know if I managed to change it.
[17:58] <s|oO|0o|g> hi, are there any best practices as far as log management for cloud-init is concerned? the best I could find is "can be deleted after 3 days" from prodisup.com "handling-logs-on-ubuntu"... TBH I've never really bothered looking into cloud-init, fast forward one year and one 20.04 server has an 11GB cloud-init.log :/
[17:59] <s|oO|0o|g> there is an open launchpad ticket from 2019 about the lack of rotation, but not much activity
[17:59] <s|oO|0o|g> now that I'm thinking about it, that's one hell of a strategy to get people to pay attention XD
[18:00] <s|oO|0o|g> now that I think*
[18:01] <s|oO|0o|g> "Read the docs and decide for yourself"?
[18:03] <holmanb> blackboxsw: sounds good, thanks!
[18:13] <mayak> root
[18:51] <minimal> s|oO|0o|g>: do you not run something like logrotate on your machines? add the cloud-init files to its config...
[20:03] <blackboxsw> s|oO|0o|g>: yeah maybe logrotate.d config something like this https://paste.ubuntu.com/p/zVD6TCPvRd/
[22:59] <blackboxsw> falcojr: holmanb or paride https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-integration-lxd_vm-jammy-daily/12/consoleFull PYCLOUDLIB_* env vars are still not being passed into our CI. Here's a PR that should fix it.
[23:02] <blackboxsw> the long awaited PR link https://github.com/canonical/cloud-init/pull/1196