vRealize Orchestrator - SSH Keys - Idea for how to easy manage multiple keys

Many are using SSH to run commands something similar to 

var passwordAuthentication = false;
var password = '';
var session = new SSHSession(hostName, username, port);
session.connectWithPasswordOrIdentity(passwordAuthentication, password, path);

Where the path leads to the private key file for the connection.

Storing several key files in the vRO filesystem could easily lead to forget it when moving to a new vRO or add a new vRO node. Also when moving forward with vRO 8 it's less of a good idea to add elements to the local filesystem as a manual step.

My suggestion for a solution is to make use of the vRO resource element.
Store your key file as a vRO resource element, using the following step of code can runtime make the key available for SSHSession.

var tempDirectory = System.getTempDirectory();
filePath = tempDirectory+ "/" + keyfile.name;
keyfile.writeContentToFile(filePath);

Send the private key file as a resource to the action or workflow and you will have the path you need for your SSH Key and any new vRO node will automatically have access to it. Also, make key management easier. 

One can use similar methods and instead of a resource element, store the key is a remote system and pull it from there and write it to the filesystem using a filewriter