> @@ -52,35 +60,55 @@ > /** > * To get a service account and its private key see [TODO: write some > * documentation on the website and put a link to it] > - * > - * The first argument (args[0]) must be your service account email address > - * The second argument (args[1]) must a path to your service account > - * private key PEM file (without a password). > + * > + * The first argument (args[0]) is your service account email address > + * (https://developers.google.com/console/help/new/#serviceaccounts). > + * The second argument (args[1]) is a path to your service account > private key PEM file without a password > + * (https://developers.google.com/console/help/new/#serviceaccounts). > + * The third argument (args[2]) is your Google user name. > + * The fourth argument (args[3]) is a path to the file containing your > SSH public key > + * (https://developers.google.com/compute/docs/instances#sshkeys). > + * The fifth argument (args[4]) is a path to the file containing your SSH > private key > + * (https://developers.google.com/compute/docs/instances#sshkeys).
Added clarifying comments and a disclaimer that private keys are not transmitted anywhere. The experience I gained when writing this example (and the way I understand the documentation) tell me that we need the PEM file for server-to-server interaction and the SSH keys to perform actions on machines. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-examples/pull/59/files#r16103288
