feat: replace ssh-private-key with ssh-private-keys and expected input is json with {name: key} entries. #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
Module https://github.com/webfactory/ssh-agent exports public keys from private keys under
.ssh/
folder and depends only on ssh-agent behaviour on selecting correct cert.When trying to pass to docker build with action which doesn't support forwarded ssh-agent then while trying to use generated key-* files then we get
invalid format
- with PEM or non-PEM / reason is that public key can not be used for ssh-git authentication.Description
With this change we export all passed private keys and use new format for input - object key should be "
[email protected]:owner/repo.git
" and we will use that one instead of trying to extract comment from public key where it potentially could be missing.Example usage