`nucypher-ops` commands that require the ssh key should allow any ssh key filepath to be specified

[derekpierre]

I like to have my ssh keys in different folder locations. However nucypher-ops ursula deploy seems to require the ssh key to be ~/.ssh/id_rsa. Ideally, I would be able to specify the filepath to any ssh to override the default. I believe --key-path is used for nucypher-ops nodes create, so something similar should be done for running nucypher-ops ursula comands.

[vepkenez]

@derekpierre the way it works is that when you --create or --add a node, the key path for that node is saved in your config file. It can be anything when you create or add the node, so in your case, it presumably was ~/.ssh/id_rsa (which is the default).

That said, we could make a way to change it or override it.

[derekpierre]

Ah ok. Is there a way for me to temporarily update that setting in a configuration file before a fix is available?

[derekpierre]

Looks like it was just a matter of adding to the provider_deploy_attrs list in the json configuration file:

"provider_deploy_attrs": [
...
    {
         "key": "ansible_ssh_private_key_file",
         "value": "<path>"
    }
],

[mickeyjoes]

{
"key": "ansible_ssh_private_key_file",
"value": ""
}

Thanks, this worked for me.
I have similar setup with multiple keys. It would be nice to have the nucypher-ops ursula deploy ask for this configuration so the deploy can continue.