Overview

A profile tells SQIBS where and how an action runs: the tool version, and the connection details such as an SSH host, a Kubernetes configuration or an Ansible inventory. One profile can be used by many workflows.

You need
Permission to manage automation profiles
Where
Automation > Profiles
Result
Reusable run environments for your actions

Profile types

Type Use it for Details
Bash Bash scripts Bash profile
Python Python scripts Python profile
SSH Commands on a remote host over SSH SSH profile
Ansible Ansible playbooks and commands Ansible profile
Terraform Terraform plans Terraform profile
Kubernetes kubectl against a cluster Kubernetes profile
PowerShell PowerShell scripts PowerShell profile
Runner Running actions inside your network with the Callgoose automation runner Runner profile

Create a profile

  1. Go to Automation > Profiles and choose Global or a team. The profile belongs to what you choose.
  2. Click Add Profile and choose the type in Select Profile Type.
  3. Fill in the details for that type (see the table above), then click Save.

Only users with the automation privilege can add, edit or delete profiles.

Edit or delete a profile

  • Open the profile card and use Edit Profile to change its name, description and details. Extra files can be uploaded under Other Files once the profile exists.
  • Use Delete Profile to remove it. SQIBS does not let you delete a profile that a workflow still uses; it lists the workflows instead.

Run other languages with the runner

With the Callgoose automation runner you can run any program installed on the runner host: Java, Go, Ruby, Node.js, PHP and more. Add a Bash (Linux, Unix, macOS) or PowerShell (Windows) internal profile under the runner profile, and call your program from the action's script:

#!/bin/bash
# Call a Ruby script
ruby /path/to/your_script.rb
# Call a Go program
/opt/tools/check-queue --max-age 300
# Call a Java program
java -jar C:\tools\report.jar
# Call a Node.js script
node C:\tools\cleanup.js