Rundeck

• Execution failedRuns when a job or command fails, is aborted or times out, in every project or the one you choose, optionally of one job. Executions that ended before the workflow was turned on don't start it.
• Execution succeededRuns when a job or command succeeds, in every project or the one you choose, optionally of one job. Executions that ended before the workflow was turned on don't start it.
• Execution startedRuns when a job or command starts, by hand, on its schedule or from another tool, in every project or the one you choose, optionally of one job. One that starts and ends between two looks starts it too.

• List projectsList the Rundeck projects the token may see, by name, with their descriptions.
• Get projectGet a project's name, description and link, with how many jobs it has and how many are scheduled.
• List jobsList or find a project's jobs by name and group, with whether each is scheduled and turned on, and its ID for the other job steps.
• Get jobGet a job's definition: its options (what a run can be given, which are required and their defaults), schedule, nodes and steps, and, if asked, its YAML to keep or import elsewhere.
• Run jobRun a job with the options you give, as Rundeck's Run Job Now button does, on its nodes or the ones you choose, now or at a set time. Turn on waiting to get how it went and the end of its log.
• Enable or disable jobTurn a job's running or its schedule off or on, as the job's menu in Rundeck does: with running off, nobody can run it; with its schedule off, it runs only when started by hand.
• Import jobMake or update a job in a project from its definition in YAML or JSON, as Rundeck exports it (Job Actions > Download) and 'Get job' gives it.
• Delete jobDelete a job, as its menu's Delete this Job does. Its past executions stay. A job that isn't there is left as it is.
• Get executionGet an execution's status, options, times and nodes, with its state on each node.
• List running executionsList the jobs and commands running now, in one project or all of them, optionally of one job.
• Find executionsFind a project's executions, the latest first, by status, job, who started them and when they ran, as the Activity page does.
• Abort executionStop a running execution, as its Kill Job button does, and wait a few seconds for it to stop. One that has already stopped is left as it is.
• Get execution outputGet the end of an execution's log, oldest line first, with the lines logged as errors, from every node or one.
• Delete executionDelete a finished execution and its log from Rundeck's history. One that isn't there is left as it is; one still running must be aborted first.
• Run commandRun a command on the nodes you choose, as Rundeck's Commands page does, such as uptime to check servers. Turn on waiting to get its output.
• List nodesList a project's nodes (the servers jobs and commands run on), all of them or those a node filter matches, with their host names, tags and attributes.
• List keysList what's in a Key Storage folder: its folders, and its passwords and keys by type and when they changed. Rundeck never gives a password or private key back.
• Store keyAdd a password, private key or public key to Key Storage, or replace the one at that path, such as after rotating a database password jobs use.
• Delete keyDelete a password or key from Key Storage. Jobs and nodes that use it stop working until it's stored again. A path with nothing there is left as it is.
• Get system infoGet the Rundeck server's version, whether it's running jobs (active) or not (passive), how many are running and how long it has been up.

No actions match that.