[01:43] Xe: nice work on that post BTW! [01:43] we were passing it around today. [01:44] same to you Mr powersj :) I hadn't seen yours [01:45] nice :D [01:45] i hope the sarcastic parts didn't come off too badly, i got an early start in the morning thanks to an amber alert (in Canada they use the "TAKE COVER YOU ARE BEING NUKED" alert level and you can't opt out of them) so it might have come off a lot more snarky than I intended [01:51] yeah same in Colo, USA. And sarcasm is the author's liberty and draws a repeated audience :). For your " What if I need to template the userdata file?" you had me thinking maybe you were going to touch on jinja templates for distro specific user-data functionality a. la https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#using-instance-data [01:58] It'd give "templaters" a chance to use things like## template: jinja [01:58] #cloud-config [01:58] runcmd: [01:58] well that surely didn't work [02:01] https://paste.ubuntu.com/p/bfdtzPGvd7/ [02:01] that's more readable. Anyhow. time to head into the weekend [02:01] cheers all [02:15] blackboxsw: i'm more touching on how i templated the yaml for integration tests at work [02:16] +1. yeah I had misunderstood initially on first glance. [02:17] does cloud-config work if you use json instead of yaml (with the right header ofc) [03:49] ahh sry. Yes, since YAML is a superset of JSON it observes JSON constructs, so something like {"runcmd": ["echo I work"]} would be honored as long as it was preceded by a header line #cloud-config [05:27] thanks, will file a issue. [05:28] do I file bug on https://bugs.launchpad.net/cloud-init/+filebug or https://github.com/canonical/cloud-init ? [05:28] it ask me to signup a ubuntu one account, which I don't have one yet. [05:28] but I do have github account. [08:21] https://bugs.launchpad.net/cloud-init/+bug/1930956. [08:21] bug filed, also I have a PR workaround the issue: https://github.com/canonical/cloud-init/pull/915