After some further discussion I think it's OK to expect that an image that has cloud-init will regenerate and remove ssh keys (on new instance) this is default cloud-init behavior.
I do think we should Conflict, but I also understand not wanting to change systems which have ssh-keygen which is currently running to a state where it's not run and users being unaware that cloud-init was handling that for them. -- https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/349359 Your team cloud-init commiters is requested to review the proposed merge of ~smoser/cloud-init:fix/1781094-ssh-deletekeys into cloud-init:master. _______________________________________________ Mailing list: https://launchpad.net/~cloud-init-dev Post to : cloud-init-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~cloud-init-dev More help : https://help.launchpad.net/ListHelp
