-
Notifications
You must be signed in to change notification settings - Fork 1
Specifying Additional SSH Keys
vzakaznikov edited this page Jan 24, 2024
·
2 revisions
In addition to the main SSH key specified by the --ssh-key option, which is used to connect to the servers, you can specify additional SSH keys using the additional_ssh_keys property in the configuration file. This is needed in cases where there is more than one user that should have access to the servers used for the runners.
✋ Note: | Additional SSH keys can only be defined using a configuration file. See Using a Configuration File for more details. |
---|
Note that the additional SSH keys are defined using only the public key. This enables additional users to hold the matching private key to connect to the servers.
For example,
config.yaml: |
config:
additional_ssh_keys:
- ssh-rsa AAAAB3Nza3... user@user-node
- ssh-rsa AADDDFFFC1... another_user@another-node |
---|
Developed and maintained by the TestFlows team.
- Home
- Installation
- Quick Start
- Getting Started Tutorial
- Basic Configuration
- Specifying the Maximum Number of Runners
- Specifying the Maximum Number of Runners Used in Workflow a Run
- Recycling Powered‐Off Servers
- Skipping Jobs
- Using Custom Label Prefix
- Jobs That Require the Docker Engine
- Specifying The Runner Type
- Specifying The Runner Location
- Specifying The Runner Image
- Specifying The Custom Runner Server Setup Script
- Specifying The Custom Runner Server Startup Script
- Disabling Setup or Startup Scripts
- Specifying Standby Runners
- Specifying Logger Configuration
- Listing All Current Servers
- Opening The SSH Client To The Server
- Deleting All Runners and Their Servers
- Using a Configuration File
- Specifying SSH Key
- Specifying Additional SSH Keys
- Running as a Service
- Running as a Cloud Service
- Scaling Up Runners
- Scaling Down Runners
- Handling Failing Conditions
- Meta Labels
- Estimating Costs
- Program Options