[09:54] <meena0> does this feel like terrible advise https://community.hetzner.com/tutorials/basic-cloud-config or is that just me?
[10:45] <meena0> it's my favourite problem, of cloud-init not recognizing it's on Hetzner
[14:06] <meena0> holmanb: tested this on Hetzner: https://github.com/canonical/cloud-init/pull/2165
[14:06] -ubottu:#cloud-init- Pull 2165 in canonical/cloud-init "Ephemeral Networking for FreeBSD" [Open]
[14:09] <meena0> i need to submit that as bug that Hetzner is correctly found by ds-identify, and then not found by cloud-init itself.
[14:10] <meena0> OTOH, the default config https://github.com/canonical/cloud-init/blob/main/config/cloud.cfg.tmpl#L60 doesn't have it
[14:13] <minimal> meena0: as L60 doesn't include Hetzner then it won't be used
[14:14] <minimal> meena0: also was there a specific part of that Hetzner doc that you thought was terrible advise?
[14:14] <meena0> minimal: what about the cloud.cfg ds-identify generates? is that included anywhere?
[14:14] <meena0> meena0: all the stuff that is sed
[14:15] <minimal> meena0: isn't ds-identify only used by systemd?
[14:17] <meena0> i dunno, I'll fire up a fresh instance to see what's going on
[14:17] <minimal> re: sed, how else would you recommend for some of those settings be changed when c-i itself doesn't provide a method to change/set them?
[14:19] <minimal> meena0: actually I asked on here about ds-identify on 22nd May as to whether it was used anywhere apart from systemd generator - answer from holmanb was no
[14:20] <meena0> ah
[14:21] <minimal> yeah I was going to make an alpine-related change to it.....and then couldn't see where alpine would use it lol
[14:22] <meena0> what's systemd generator?
[14:22] <minimal> so if you add Hetzner to datasource_list (whether in cloud.cfg or if you drop an additional file into /etc/cloud.cfg.d/ directory to override it) it should work
[14:23] <minimal> its used by cloud-init running on systemd, that's all I know as I don't need to know more as I don't use cloud-init with systemd ;-)
[14:23] <meena0> i need to see if dropping that line works
[14:23] <minimal> dropping which line?
[14:23] <meena0> 60
[14:23] <minimal> or override it as I mentioned
[14:24] <minimal> that's what I do in my disk images
[14:25] <minimal> e.g. create a file /etc/cloud/cloud.cfg.d/01-datasources.conf with only a single line in it: "datasource_list: ['abc', 'def', 'ghi']"
[14:26] <meena0> i'm just trying to improve the out of box experience
[14:28] <minimal> dunno why that line is there in the 1st place. If you remove it then the "builtin" list of all datasources will be used
[14:30] <minimal> which comes from here: https://github.com/canonical/cloud-init/blob/main/cloudinit/settings.py#L22
[14:36] <meena0> *weird*
[14:37] <meena0> also weird: docs lint failed on  me, on a document i didn't touch
[14:38] <meena0> it's from https://github.com/canonical/cloud-init/pull/2133
[14:38] -ubottu:#cloud-init- Pull 2133 in canonical/cloud-init "Update kernel commandline docs (SC-1457)" [Merged]
[15:32] <minimal> I've been getting emails from github the past several days about "scheduled: All jobs have failed" in my *fork* of cloud-init. Is this some side-effect of the .github stuff in the cloud-init repo?
[15:34] <minimal> looking at the "Actions" tab of *my fork* of cloud-init I see info about 15 workflow runs - does this mean everyone who forks canonical/cloud-init is having actions run also?
[15:37] <falcojr> I believe so...but also we need to fix what's failing (it fails upstream too)
[15:37] <minimal> so there's no way for me to have a fork of cloud-init without any actions being run?
[15:38] <falcojr> I believe you can disable repo actions in the settings
[15:39] <minimal> ok, I'll check. It seems a bit strange, and perhaps a bit of a security-type issue, that anyone forking a github repo with actions also has actions run in their fork by default
[15:39] <dbungert> I wonder if some actions can run.  On a different repo it's kind of nice to run the CI on my branch directly, pre PR.  The scheduled jobs may not make sense in that case though.
[16:55] <meena0> i thought i had fixed all the tests on https://github.com/canonical/cloud-init/pull/2146
[16:55] -ubottu:#cloud-init- Pull 2146 in canonical/cloud-init "FreeBSD fix parsing of mount and mount options" [Open]
[20:15] <holmanb> meena0: hrm, doesn't look like it
[20:19] <meena> that pr keeps slipping away from me
[22:42] <meena0> another easy one, i hope: https://github.com/canonical/cloud-init/pull/4159
[22:42] -ubottu:#cloud-init- Pull 4159 in canonical/cloud-init "BSD: remove datasource_list from cloud.cfg template" [Open]
[23:09] <hyperreal> Hi. Is it possible to enable suites for Debian, similar to how there is a disable_suites option for the APT module? https://cloudinit.readthedocs.io/en/latest/reference/examples.html#additional-apt-configuration-and-repositories
[23:09] <hyperreal> I'd like to enable the backports repo