1.4.0
Added
- An alert comes in: a trigger that runs when the Alerts plugin gets an alert, picked by category, severity, title and host, so an automation can restart a service when its Uptime monitor goes down (needs Alerts 1.4.0)
1.3.0
Changed
- The automations panel puts search and the add button on one row on Termix 26.11.2 and later
- Runs in its own process on Termix 26.11.2 and later, with no access to the server beyond what Termix allows it
- Hosts in a maintenance window show a dot on their row instead of a badge
- Its process stops when it has nothing to watch or run, and Termix starts it again when there is work, which saves memory on Termix 26.11.2 and later
- The settings button in the Automations panel opens the Automations page in Settings
1.2.1
Added
- Run an automation as a Termix action, from the command palette, the CLI, the phone app or another automation
- Run an action step: any action a plugin offers, with its own form, on the trigger host, picked hosts or a fleet
- An event happens trigger: start an automation when a plugin reports an event or an action fails
- A failed runs status tile and a homepage widget with the latest runs
Fixed
- The automations dashboard card scrolls as one list instead of squeezing your automations and runs into two small boxes
Changed
- Needs Termix 26.11.1 or newer
- The maintenance page and the Automations tab use the Termix page header and tile look
- Form labels match the rest of Termix
- Toolbars, loading screens, back buttons and Save bars match the rest of Termix
1.2.0
Added
- Automations panel beside an SSH terminal: the host's maintenance state, the automations that use the host with Run now, and their latest runs
- Upcoming automations dashboard card: scheduled automations in the order they run next
- Automation runs dashboard card: the latest runs and how they went
1.1.0
Added
- A per host Enable maintenance switch in the host editor, off by default
Changed
- The Maintenance button only shows on hosts that have the switch on
1.0.3
Fixed
- The run limit (
maxRunSeconds) can be set when creating an automation over HTTP and changed afterwards; before, only the service could set it, once
1.0.2
Added
automations.access create takes concurrencyPolicy and maxRunSeconds, so plugins can create automations with a longer run limit
- Set a timeout per step for commands, snippets and HTTP calls (60 seconds by default)
- Ask AI step, which has the AI Assistant look into a problem on your hosts and report back or propose a fix for approval
Changed
- The plugin name and description show in your language
Fixed
- Metric triggers kept their hosts' metrics alive every 15 seconds and filled the audit log; they now check in once a minute
- A step that timed out with Carry on set left the run marked as successful
1.0.1
Changed
- Translated into every supported language
1.0.0
Added
- First release
- Triggers for metrics, hosts going up or down, health checks, schedules, container events and webhooks
- Steps that run commands and snippets, control containers and tunnels, wake hosts, call URLs and send alerts, with values from triggers and variables always passed safely into shell commands
- Conditions, waits and variables for more complex flows, and nested steps that only run automations you own
- Run on one host, a fleet or every host
- Test runs and a history of every run
- Maintenance windows that pause automations while you work on a host