Terms

Name

Definition

Template

A file in YAML or JSON format that includes one or more tasks.

Task

The main component of a template. It defines the details of an action. Each task is a specific implementation of an action.

Action

An action defines a specific operation and is the smallest operational unit. There are several types of actions: API action (Atom Action), cloud product action (Product Action), trigger action (Trigger Action), control action (Control Action), and embedding action (ACS::Template). The name format is ACS::<Name>.

API action

An action that lets you call an API. Currently, ACS::ExecuteAPI, ACS::WaitFor, and ACS::CheckFor are supported.

Cloud product action

An action that wraps the business logic and OpenAPI features of a cloud product to simplify template creation. For example, after the ACS::ECS::RunInstances action successfully runs, it ensures that the created instance enters a usable state, such as `running`. The name format is ACS::<ProductCode>::<Name>.

Trigger action

When enabled, this action executes a template when its trigger source meets specific conditions. The currently supported trigger action is TimerTrigger.

Control action

Controls the execution order or method, such as the approval action ACS::Approve.

Embedding action

Currently, only ACS::Template is supported. This action lets you reference other templates (child templates) as tasks and supports custom, reusable child templates. A template that references child templates is called a parent template.

Execution

The result of a template execution, either in progress or completed.

Task execution

The result of a task execution, either in progress or completed.

Loop task

A task that runs repeatedly, using a different value from a list for each iteration.