shy-refrigerator-41911
04/28/2025, 8:18 AMconst tlsServerKey = new tls.PrivateKey('TlsServerKey', { algorithm: 'ED25519' })
const sshKey = new hcloud.SshKey('SshKey', { publicKey: tlsServerKey.publicKeyOpenssh })
const server = new hcloud.Server('Server', {
image: 'debian-12',
serverType: 'cax21',
location: 'fsn1',
sshKeys: [sshKey.id],
})
Let's ignore that I'm generating a key rather than supplying my own for this example. If I were to rotate the key somehow I would assume that a completely new server is going to be provisioned with the previous one being removed. Technically not a big issue however I have a ton of steps on top of it to bootstrap the system. Is it even worth to investigate a proper rotation on the same machine?quick-house-41860
04/28/2025, 10:31 AMsshKeys
property is marked as replacing, so changing them will trigger the recreation of the server. The hetzner docs mention that you cannot update the ssh keys: Once the server is created, you can not update the list of SSH Keys.
Alternatively, you could add the new SSH key directly on the VM itself instead of going through the Hetzner Cloud APIs: https://community.hetzner.com/tutorials/add-ssh-key-to-your-hetzner-cloud#step-5---add-an-ssh-key-to-an-already-created-serverquick-house-41860
04/28/2025, 10:32 AMshy-refrigerator-41911
04/28/2025, 12:39 PMNo matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.
Powered by