Tom Parrott
Tom Parrott
> I think that it would probably be preferred if we can exercise this code path in cloud-init using LXD, but I do think that doing both would conflict. Maybe...
@blackboxsw does cloud-init apply the existing `user.meta-data` on every boot or only first boot?
@holmanb @blackboxsw hi, does cloud-init apply the existing user.meta-data on every boot or only first boot?
> I think that it would probably be preferred if we can exercise this code path in cloud-init using LXD, but I do think that doing both would conflict. Maybe...
> we have a second use case for the user of `user.meta-data` in integration testing of lxd which allows cloud-init to inject default [SSH public-keys configuration into all images launched...
Thanks @holmanb @hamistao and I were discussing this the other day and our plan at this time is as follows: 1. Add support for `cloud-init.ssh-keys.NAME` keys that can take either...
Agree, it would need to be sequential not parallel/concurrent though as the token is single use.
Similar discussion here: https://github.com/lxc/incus/issues/1020#issuecomment-2262087040 https://github.com/lxc/incus/pull/1127
@simondeziel may have thoughts around this too.
@boltmark can you identity which commit introduce that issue please, thanks