[11:25] it's interesting to see how the runcmd module documentation shows the array of strings indented but the write_files one does not indent the array of objects, is that part of the yaml syntax [11:26] ? [13:52] esv: It changes how cloud-init interprets and executes the data. See https://cloudinit.readthedocs.io/en/latest/topics/modules.html#runcmd: [13:52] > Run arbitrary commands at a rc.local like level with output to the console. Each item can be either a list or a string. If the item is a list, it will be properly executed as if passed to execve() (with the first arg as the command). If the item is a string, it will be written to a file and interpreted using sh. [13:55] I think what makes the Examples confusing in the runcmd module's docs is the fact they *include* stuff like [ sh, -c, echo, ...], when in fact that means that will be written to a file and then you will get "/bin/sh temp-file.sh" where the temp file also includes "sh -c echo". :) [13:55] Wait, sorry, I had that backwards. If the item is a string it is written to a file. [13:55] Mea culpa. [13:56] This is where if we used Slack I would just delete the misleading bit above. As it is, my mistake gets to live in infamy forevvvvvveeerrrrrrrrr. Or at least until the energy death of the universe or the IRC logs are reset. Whichever comes first :) [14:30] Hi All, Can someone tell me why Centos 7 is not building newer releases of Cloud-init after 19.4 ? I assume it will a big duhh... but haven't found an answer online yet. Thanks in advance! === Guest9865 is now known as andrewbogott [14:49] xtalk: 19.4 is the last python2.X cloud-init release; I don't think centos7 has official python3 support (or possibly not enough of the python3 modules to support cloud-init) https://lists.launchpad.net/cloud-init/msg00227.html [14:54] rharper Thanks for the link, my google fu was not strong enough :( a pretty obvious reason indeed. [14:54] xtalk: sure , it's one of those, if you don't know to search for python 2.X EOL then it doesn't really show up