Overview
Keep your actions and profiles in your own Git repository instead of in SQIBS. You version and review them like any code; SQIBS fetches them when the workflow runs. Each action or profile points at one entry file: a small YAML file that says which files to use and how.
You need
A Git repository SQIBS (or your runner) can reachWhere
Any action or profileResult
Versioned automation in GitConnect to your repository
| Field | What to enter |
|---|---|
| Git Auth Type | Token (recommended), SSH (a key pair) or Basic (user name and password; not recommended). |
| Git Url | Token or Basic: https://git.example.com/team/automation.git. SSH: use the ssh:// form, for example ssh://git@git.example.com/team/automation.git (not git@git.example.com:team/automation.git). |
| Git File Path | The path of the entry file from the repository root, for example action/bash/check_disk_space/cg_entry_file.yaml. |
| Git Branch | Leave empty for the default branch. |
SSH keys
- On the Callgoose cloud: add the public key SQIBS shows on the automation profile to your Git server.
- On your automation runner: put the key and an SSH config in
~/.sshof the runner's user. Supported key files:id_rsa,id_dsa,id_ecdsa,id_ed25519.
# ~/.ssh/config on the runner host
Host git.example.com
IdentityFile ~/.ssh/id_ed25519
ConnectTimeout 10
Add the Git server to ~/.ssh/known_hosts (connect once by hand) rather than turning host key checking off.
The entry file
Put each action's (or profile's) files in their own folder with the entry file next to them. You can name the entry file as you like, for example cg_entry_file_action_python.yaml. SQIBS offers a ready-made entry file for each type to download; the formats are also on action entry files and profile entry files.
automation/
action/
bash/
check_disk_space/
cg_entry_file.yaml
check_disk_space.bsh