I really don't know what you're expecting to hear.
cloud-init is guaranteed to run Before ssh-keygen.
Worst case,
a.) ssh-keygen creates keys that cloud-init didn't write (but since cloud-init deleted *all* keys on new-instance, this actually works pretty well).
b.) ssh-kegen does nothing and wastes some 'stat' of files that it would have executed.
I guess we could drop-in a 'disable' of keygen-service on package install. that just seems like more work than necessary.
I really don't know what you're expecting to hear.
cloud-init is guaranteed to run Before ssh-keygen.
Worst case,
a.) ssh-keygen creates keys that cloud-init didn't write (but since cloud-init deleted *all* keys on new-instance, this actually works pretty well).
b.) ssh-kegen does nothing and wastes some 'stat' of files that it would have executed.
I guess we could drop-in a 'disable' of keygen-service on package install. that just seems like more work than necessary.