On Fr., 27. Dez. 2019 at 23:46 Uhr Noah Meyerhans <[email protected]> wrote: > Yes, but the workaround I provided completely replaces the missing > functionality. IMO if the docs described the process in the workaround, > rather than the existing behavior based on apt-key, we'd be done.
I think the workaround is perfectly fine. Actually I am already passing the PGP key as "key" block to cloud-init, but it is making use of apt-key add anyway. Just placing it in /etc/apt/trusted.gpg.d/foo.gpg via write_files is the better solution imho. I'm doing the very same thing for my CentOS-based cloud-init image bootstrapping process (just to a different path: /etc/pki/rpm-gpg). There is no workaround for the lack of vlan and bridge-utils though. It would be great it we could get those two included into the base image. Repairing /etc/network/interfaces to include cloud-init generated network configs would also be great. I still have to check if a workaround (also using write_files) would work here too, but I think network setup is executed even before that stage too. Best regards, Christian
