=== cpaelzer__ is now known as cpaelzer
[17:06] <Odd_Bloke> rharper: blackboxsw: https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/371053 <-- should be ready for re-review
[17:07] <Odd_Bloke> (Don't land it yet though, I'll want to do a final smoke test on Oracle with all changes included before it lands.)
[17:39] <rharper> Odd_Bloke: cool
[20:34] <danielmarquard> o/ hello! curious if anyone could provide guidance or a link to documentation on how and where cloud-init executes user data and downloads public keys. we track a single config for our centos AMI, built on-prem. it creates a user, but doesn't explicitly make any mata data calls, yet userdata executes by default. trying to understand how cloud-init knows to do these things by default and how the behavior can be changed
[21:00] <rharper> danielmarquard: hi,  depending on the platform you launch an instance, the Datasource used is different, for example on EC2, cloud-init will certain metadata calls per that class, and if launched in Azure, it will make others.    what exactly do you need to do?
[21:02] <rharper> https://cloudinit.readthedocs.io/en/latest/topics/modules.html#ssh  https://cloudinit.readthedocs.io/en/latest/topics/modules.html#ssh-import-id are two modules which can import ssh keys
[21:43] <danielmarquard> rharper, thanks for the docs. ultimately, we need to ensure that our custom runcmd stanza executes before userdata
[21:44] <rharper> you likely want bootcmd
[21:44] <rharper> that runs early
[21:44] <danielmarquard> perfect, that sounds about right. thanks for the guidance :)
[21:46] <rharper> danielmarquard: it's worth looking at /etc/cloud/cloud.cfg to see the config_*_module lists,   that shows the order in which modules are run;  bootcmd runs early, but it also runs before the user is created; so that may present a problem depending on your script.
[21:48] <danielmarquard> we're expanding all partitions in the root volume on a per-instance basis. will keep that module prioritization in mind. thanks!