[08:01] sheesh === FergusL2 is now known as FergusL [13:31] hi, is it possible to provide run-once scripts in userdata? [13:33] Nothing4You: https://cloudinit.readthedocs.io/en/latest/topics/examples.html#run-commands-on-first-boot [13:34] That's an example of cloud-init-per [13:34] But you probably want to use it against runcmd instead (the following example) [13:35] rbasak: i was intending to run stuff in the final stage which this would be part of https://cloudinit.readthedocs.io/en/latest/topics/modules.html#scripts-per-once [13:36] i guess a workaround could be to create the script in bootcmd/runcmd and write it to a file that will be loaded in the final stage [13:38] Nothing4You: is that not the equivalent of https://cloudinit.readthedocs.io/en/latest/topics/modules.html#runcmd anyway? [13:38] In terms of stage. [13:39] runcmd runs in the config stage [14:11] Nothing4You: runcmd runs during config stage, but all it does there is write the script to /var/lib/cloud/instances/scripts [14:12] the script gets executed via the scripts-user module in the final phase [14:12] ah, thanks [14:13] if i specify package_reboot_if_required=true, does that reboot happen as part of the package-update-upgrade-install module before processing the other final stage modules? === arif-ali- is now known as arif-ali [20:25] yes [20:25] Nothing4You: ^. it happens when installing packages and then reboots before going further. [20:25] and then picks up again. [20:26] but that only works on debian/ubuntu [20:26] thanks [20:26] debian in my case, so that's fine [20:32] it relies on /var/run/reboot-required or some such being written. so ... i spoke without verifying that. [20:32] but it does work on ubuntu [20:34] it's definitely rebooting my debian 10 machines