Task Debugging in CloudOps Orchestration Service (OOS) lets you step through a template one task at a time, similar to breakpoint debugging in programming. You run each task individually, inspect its results, and then advance to the next task. This helps you verify that each task works correctly before you run the full workflow.
Prerequisites
Before you begin, make sure that you have:
-
Access to the CloudOps Orchestration Service console
-
A custom template to debug, or access to the sample templates
How task debugging works
When you click Task Debugging, OOS creates a temporary execution and pauses before the first task. You then advance through tasks one at a time, choosing whether to use the execution's parameters or override them for each task. After you finish, click Stop Debugging to close the dialog box and automatically delete the temporary execution.
-
Debugging affects real cloud resources. Operations performed during debugging take effect on the relevant cloud resources. They are not sandboxed.
-
If you do not click Stop Debugging, the temporary execution is not automatically destroyed. To manually remove it, see Cancel an execution and Delete an execution.
-
Debugging may incur costs for the cloud resources involved. Use the price calculator to estimate costs before you start.
UI elements
|
UI element |
Description |
|
Task Debugging |
Starts debugging. Opens the Task Debugging dialog box and creates a temporary execution. |
|
Edit Template Parameter |
The step where you configure template parameters. |
|
Perform Task of Single Step |
The step where you run a single task for debugging. |
|
Execute |
Runs the selected task. |
|
Use Parameters Provided by Current Execution |
Uses the parameter values from the current execution. Selected by default. |
|
Override Parameters Provided by Current Execution |
Lets you manually specify the input parameters for the task. |
|
Stop Debugging |
Stops debugging. Closes the Task Debugging dialog box and deletes the temporary execution. |
Example: debug the ACS-OOS-ExampleBulkyExecuteCommandsInEcs template
This example uses the ACS-OOS-ExampleBulkyExecuteCommandsInEcs sample template to demonstrate the full debugging workflow.
Procedure
-
Log on to the CloudOps Orchestration Service console. In the left-side navigation pane, choose . On the Custom Template page, click Create Template.
-
On the Create Template page, select Create Template Based on Samples, and then select the ACS-OOS-ExampleBulkyExecuteCommandsInEcs template in the Edit Template Parameter step. Click Next Step.
-
On the Process Configuration tab, click Task Debugging. The Task Debugging dialog box appears.
-
Manually select instances and click Next Step.
-
Find the first task and click the task name. In the displayed task information, select one of the following options in the Required Parameters section:
-
Use Parameters Provided by Current Execution: Uses the parameters configured for the execution. Then, click Execute to the right of the task name.
-
Override Parameters Provided by Current Execution: Manually configure the input parameters for the task. Then, click Execute to the right of the task name.
-
-
Find the second task and click Execute to the right of the task name. Click the task name to view the execution results.
-
Click Stop Debugging.