Unable to specify private key in std ssh action
Bug #1806703 reported by
Jose Castro Leon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The standard ssh action relies in having the private keys installed in the mistral-executor. The user specifies the name of the key and it will lookup locally and use it for the ssh connection.
The idea is to allow to pass by parameter the private key that's going to be used in the ssh connection avoiding storing and handling private keys in the executor filesystem.
The private key could be passed by parameter in the action and in a workflow this key could be stored in barbican and retrieved in a previous action.
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/622339 /git.openstack. org/cgit/ openstack/ mistral/ commit/ ?id=9bbc1d41d0a 9cf8d4605a552e3 fceb25c7dc4341
Committed: https:/
Submitter: Zuul
Branch: master
commit 9bbc1d41d0a9cf8 d4605a552e3fceb 25c7dc4341
Author: Jose Castro Leon <email address hidden>
Date: Tue Dec 4 15:43:26 2018 +0100
Adds private_key parameter in the standard ssh actions
This method allows to specify a private key and avoids its storage
in the filesystem of the executors. This can be used later in
combination of a secrets_retrieve to use keys stored in barbican.
Change-Id: Ide438a7f6d24c8 bdc9eb2c82e935f d39a6acc2c6
Closes-Bug: #1806703