ssh-agent/action.yml

name: 'webfactory/ssh-agent'
description: 'Run `ssh-agent` and load an SSH key to access other private repositories'
inputs:
    ssh-private-key:
        description: 'Private SSH key to register in the SSH agent'
        required: true
    ssh-auth-sock:
        description: 'Where to place the SSH Agent auth socket'
runs:
    using: 'node12'
    main: 'dist/index.js'
    post: 'dist/cleanup.js'
branding:
    icon: loader
    color: 'yellow'
Write GH action to set up ssh keys for private repos 2019-09-14 22:28:16 +00:00			`name: 'webfactory/ssh-agent'`
			description: 'Run `ssh-agent` and load an SSH key to access other private repositories'
			`inputs:`
			`ssh-private-key:`
			`description: 'Private SSH key to register in the SSH agent'`
			`required: true`
			`ssh-auth-sock:`
			`description: 'Where to place the SSH Agent auth socket'`
			`runs:`
			`using: 'node12'`
			`main: 'dist/index.js'`
Randomize SSH auth socket, kill agent to support non-ephemeral, self hosted runners (@thommyhh, #27) Thanks to @thommyhh for this contribution! Unless the `SSH_AUTH_SOCK` is configured explicitly, this change will make the SSH agent use a random file name for the socket. That way, multiple, concurrent SSH agents can be used on non-ephemeral, self-hosted runners. A new post-action step will automatically clean up the running agent at the end of a job. Be aware of the possible security implications: Two jobs running on the same runner might be able to access each other's socket and thus access repositories and/or hosts. 2020-05-18 09:08:29 +02:00			`post: 'dist/cleanup.js'`
Write GH action to set up ssh keys for private repos 2019-09-14 22:28:16 +00:00			`branding:`
Replace invalid icon 2019-09-15 00:33:18 +02:00			`icon: loader`
Write GH action to set up ssh keys for private repos 2019-09-14 22:28:16 +00:00			`color: 'yellow'`