[14:38] holmanb: is there any way to construct the default home_dir in FreeBSD to be /home in FreeBSD 14.0+? [15:32] Hello, all.  Hoping to get some guidance on Jinja templates with cloud-init 22.1 on RedHat 8.  I have a template that I'm putting in /etc/cloud/cloud.cfg.d. However when it runs I get a parse error, however if I remove the file from the cfg.d folder and execute it with --format it produces the correct output. [15:32] Here is a simplified template to illustrate the problem. [15:32] ## template: jinja [15:32] #cloud-init [15:32] runcmd: [15:32] {{ ds.meta_data.imds.compute.tagsList | selectattr('name', 'equalto', 'domain') | list }} [15:32] Executing with a template in cloud.cfg.d [15:32] sudo cloud-init query --format="$( cat /etc/cloud/cloud.cfg.d/02-resolv-conf.cfg )" [15:32] WARNING: Failed loading yaml blob. Invalid format at line 5 column 1: "while scanning a simple key [15:32]   in "", line 5, column 1: [15:32]     {{ ds.meta_data.imds.compute.tag ... [15:32]     ^ [15:32] could not find expected ':' [15:32]   in "", line 6, column 1: [15:32]     ^" [15:32] ## template: jinja [15:32] #cloud-init [15:32] runcmd: [15:41] ShaneAH: "#cloud-init" ? that should be "#cloud-config" [15:43] Great catch, I can change that but the same code works on Suse15 with cloud-init 23 [15:45] changed to cloud-config, same error [18:49] meena: FYI, holmanb is out this week and I don't know the answer to your question [18:54] ShaneAH: Jinja templating in /etc/cloud/* wasn't a feature until 22.4. [19:26] Nuts, missed it by that much!! [22:50] I'm seeing strange output when packaging cloud-init git main but don't see this with 23.3: https://tpaste.us/papW [22:54] this seems to be referring to the contents of the sysvinit/freebsd/*.tmpl and systemd/*.tmpl files [23:27] minimal: why would your packaging for Alpine touch those paths? [23:29] my packaging doesn't [23:31] this is when "python3 -m pytest" and "python3 setup.py install" are run [23:31] note the line at the top is the final result of the testing portion [23:32] so this seems to be generated when "python3 setup.py install" is run [23:37] to be more precise, this is what is run: python3 setup.py install --prefix=/usr --root="" --init-system=sysvinit_openrc