Overview

An action is one task a workflow runs: a Bash or Python script, a PowerShell script, a command over SSH, an Ansible playbook, a Terraform plan or kubectl commands. Start from scratch, or copy one of the ready-made Callgoose actions and adapt it.

You need
Permission to manage automation actions
Where
Automation > Actions
Result
Tasks you can chain in workflows

Action types

Type What it runs Details
Bash A Bash script Bash action
Python A Python script Python action
SSH One command on a remote host SSH action
Ansible A playbook, or Ansible commands Ansible action
Terraform Terraform apply, destroy or commands Terraform action
Kubernetes A Kubernetes file (apply), or kubectl commands Kubernetes action
PowerShell A PowerShell script PowerShell action

Create an action

  1. Go to Automation > Actions and choose Global or a team.
  2. Click Add Action and choose the type in Select Action Type.
  3. Optional: click Copy From to start from an existing action: a Callgoose action (ready-made, free to use and change), or one of your team or global actions.
  4. Fill in the details for that type, then click Save.

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

Fields every action has

Field What it means
Name, Description What the action does, so others can find it.
Have Argument Yes if the workflow passes arguments to the script or command.
Files from Git or Callgoose Keep the files in SQIBS, or in your own Git repository. See automation with Git.
Success Exit Code The exit status that means success. On Linux this is usually 0.
Expected Run Time(in Minutes) How long SQIBS waits (1 to 60 minutes). If the action has not finished by then, it counts as failed.

Edit or delete an action

  • Open the action and click Edit to change it. Extra files can be added under Other Files once the action exists (Ansible, Terraform and Kubernetes).
  • Click Delete Action to remove it. SQIBS does not let you delete an action that a workflow still uses.

Run other languages

Call any program from a Bash or PowerShell action, as long as it is installed where the action runs (for example on your automation runner host):

#!/bin/bash
# Call a Ruby script
ruby /path/to/your_script.rb
# Call a Go program
/opt/tools/check-queue --max-age 300