Closed MislavSag closed 3 years ago
You do not need ssh for the first one since it uses your DO credentials to list droplets. Only the second one use ssh. Have you up your ssh key on DO?
https://github.com/sckott/analogsea see Authenticate section.
Yes. I have done the following:
.Renviron
file:
DO_PAT='my api key'
I can see key in .ssh folder: 68.183.220.71 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJV7SfnS7Uqaz54dBu8JdfWNq/C1QKw20k9CPdglG5bj
I'm unable to replicate the error, sorry.
Can you provide a code sample that replicates the error on your and the content of sessionInfo()
I have finally solved the issue. I have created a new droplet and define a new ssh key while I was making a new droplet and not just in the settings!
I am waiting right now do_provision
to finish. I hope it would work.
When you do that, you have to explicitly provide your ssh keys to do_provision because they can not be autodetected.
How can I "provide my ssh keys"? I don't see argument in the function for ssh keys. Is this connected with this: https://github.com/meztez/plumberDeploy/issues/10?
Throught ...
in do_provision
see ?analogsea::droplet_create
ssh_keys parameter.
If your droplet was alreay created, you would have to add the ssh_keys to your droplet manually. Which is out of scope for this package. Better to add the ssh keys first to your DO account, then run do_provision
.
So I should:
plumberDeploy::do_provision(dropletid)
?
If I use
droplets
function fromanalogsea
package, I get the output as expectsd:but if I try:
I get an error:
If I got it right, both functions require ssh, but it works with first and not with second?