Description
Using sshUserPrivateKey on Jenkins, creates a secret ssh key.
This file however, is temporary and is given a random name, and is then removed after the pipeline is run. I'd say this is pretty secure, since there is no fishing or scraping for the ssh key possible.
However, this is invalid with the way that playbooks work right now. If the ssh_key var changes, it wants to rerun the whole playbook, even though no state has changed.
Like, I dont want to redeploy my whole database, just because the ssh key location has changed
Note: This probably sucks for people that one day want to move their ssh key to a different directory
Description Using
sshUserPrivateKeyon Jenkins, creates a secret ssh key.This file however, is temporary and is given a random name, and is then removed after the pipeline is run. I'd say this is pretty secure, since there is no fishing or scraping for the ssh key possible.
However, this is invalid with the way that playbooks work right now. If the ssh_key var changes, it wants to rerun the whole playbook, even though no state has changed.
Like, I dont want to redeploy my whole database, just because the ssh key location has changed
Note: This probably sucks for people that one day want to move their ssh key to a different directory