Closed ephemer closed 1 year ago
I think you should use private_key = file(local_sensitive_file.ssh_private_key.filename)
to get the content of your private key. The private_key
isn't a file path.
Ok so lambdalabs_ssh_key.primary.private_key
will just work then probably, which is what I was looking for in the first place. Thanks!
Hi, just wondering what you consider the best way to use the provisioner "file" / "remote-exec" APIs with an ssh private key provisioned with the lambdalabs provider?
Right now I have this, which doesn't work:
It would be ideal if we could just write:
directly, but there is a mismatch in the datatypes currently.
How do you normally achieve this? In the example you are referencing a local private key directly, but that goes against the recommendation of the repo to use a private key provisioned by the provider.