You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CHANGELOG.md
+21-1
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,23 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
## [Unreleased]
9
9
10
-
## v0.2.0
10
+
## v0.4.0
11
+
12
+
### Changed
13
+
14
+
* A failure to kill the agent in the post-action step will no longer fail the workflow run. That way, you can kill the agent yourself when necessary (#33).
15
+
16
+
## v0.3.0 [2020-05-18]
17
+
18
+
### Added
19
+
20
+
* A new post-action step will automatically clean up the running agent at the end of a job. This helps with self-hosted runners, which are non-ephemeral. (@thommyhh, #27)
21
+
22
+
### Changed
23
+
24
+
* Unless the SSH_AUTH_SOCK is configured explicitly, the SSH agent will now use a random file name for the socket. That way, multiple, concurrent SSH agents can be used on self-hosted runners. (@thommyhh, #27)
25
+
26
+
## v0.2.0 [2020-01-14]
11
27
12
28
### Added
13
29
@@ -16,3 +32,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
16
32
17
33
* Catch empty ssh-private-key input values and exit with a helpful
Copy file name to clipboardexpand all lines: README.md
+6-6
Original file line number
Diff line number
Diff line change
@@ -27,9 +27,9 @@ jobs:
27
27
...
28
28
steps:
29
29
- actions/checkout@v1
30
-
# Make sure the @v0.3.0 matches the current version of the
30
+
# Make sure the @v0.4.0 matches the current version of the
31
31
# action
32
-
- uses: webfactory/ssh-agent@v0.3.0
32
+
- uses: webfactory/ssh-agent@v0.4.0
33
33
with:
34
34
ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY }}
35
35
- ... other steps
@@ -44,7 +44,7 @@ In that case, you can set-up the different keys as multiple secrets and pass the
44
44
45
45
```yaml
46
46
# ... contens as before
47
-
- uses: webfactory/ssh-agent@v0.3.0
47
+
- uses: webfactory/ssh-agent@v0.4.0
48
48
with:
49
49
ssh-private-key: |
50
50
${{ secrets.FIRST_KEY }}
@@ -55,10 +55,10 @@ In that case, you can set-up the different keys as multiple secrets and pass the
55
55
The `ssh-agent` will load all of the keys and try each one in order when establishing SSH connections.
56
56
57
57
There's one **caveat**, though: SSH servers may abort the connection attempt after a number of mismatching keys have been presented. So if, for example, you have
58
-
six different keys loaded into the `ssh-agent`, but the server aborts after five unknown keys, the last key (which might be the right one) will never even be tried.
58
+
six different keys loaded into the `ssh-agent`, but the server aborts after five unknown keys, the last key (which might be the right one) will never even be tried. If you don't need all of the keys at the same time, you could try to `run: kill $SSH_AGENT_PID` to kill the currently running `ssh-agent` and use the action again in a following step to start another instance.
59
59
60
60
## Exported variables
61
-
The action exports `SSH_AUTH_SOCK` and `SSH_AGENT_PID` through the Github Actions core module.
61
+
The action exports the `SSH_AUTH_SOCK` and `SSH_AGENT_PID` environment variables through the Github Actions core module.
62
62
The `$SSH_AUTH_SOCK` is used by several applications like git or rsync to connect to the SSH authentication agent.
63
63
The `$SSH_AGENT_PID` contains the process id of the agent. This is used to kill the agent in post job action.
64
64
@@ -118,7 +118,7 @@ To actually grant the SSH key access, you can – on GitHub – use at least two
118
118
As a note to my future self, in order to work on this repo:
119
119
120
120
* Clone it
121
-
* Run `npm install` to fetch dependencies
121
+
* Run `yarn install` to fetch dependencies
122
122
* _hack hack hack_
123
123
* `node index.js`. Inputs are passed through `INPUT_` env vars with their names uppercased. Use `env "INPUT_SSH-PRIVATE-KEY=\`cat file\`" node index.js` for this action.
124
124
* Run `npm run build` to update `dist/*`, which holds the files actually run
0 commit comments