Overview
An SSH profile holds what SQIBS needs to run commands on a remote host: the connection details. Create it once and use it in any workflow. You can create it on the Callgoose cloud, or as an internal profile of a runner to run inside your network.
You need
Permission to manage automation profilesWhere
Automation > ProfilesResult
A reusable SSH environmentCreate the profile
- Go to Automation > Profiles, choose Global or a team, click Add Profile and choose SSH. For a runner, open the runner profile instead and add the SSH profile under Internal Profiles.
- Fill in the fields below and click Save.
| Field | What to enter |
|---|---|
| Name, Description | What the profile is for. |
| Files from Git or Callgoose | Keep the profile files in SQIBS, or in Git with a profile entry file. |
| SSH User | The user to connect as (without user@). |
| SSH Host | The host name or IP address. |
| SSH Port | Usually 22. |
| SSH Options | Optional, for example -o ConnectTimeout=10. |
| SSH Command To Run | Runner internal profiles only: the SSH client command, for example ssh. |
For cloud SSH profiles, SQIBS shows a public key on the profile (Copy key, Download Key). Add it to ~/.ssh/authorized_keys of the SSH user on the host.
Use it
In a workflow, choose this profile for each SSH action. If the action runs on a runner, choose the Runner Internal Profile instead.