add option use-base64 for encoded key #192
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It would be great to have this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello,
we try to use act to run a workflow locally. The problem is, in
actwe can not input the ssh-key as secret as multi-lines using the.actrcconfig file. One solution is, the ssh-key is base64 encoded and can be passed toactusing the.actrcfile. From the actionssh-agentthe string will be base64 decoded before it is passed to the commandssh-agent - ....This behaviour is controlled by an additional option
use-base64.Please review the changes and make a decision ob this PR should be merged. Thanks!
Best regards,
Li Sheng