Run Cloud Actions

Running Cloud Actions is very similar to running other Actions, but we wanted to provide some helpful tips that are specific to Cloud Actions. For full details, see Running Actions.

Run Action

When running the Action:

• The Actor's Location information (Local or Cloud) does not impact which Actors can be used when running Cloud Actions.
• If the Action includes Inputs, the runtime parameters are automatically expanded to display the inputs, allowing you to modify them.
• The Cloud Profiles are listed in the drop downs. 
• If there are no Inputs and no Cloud Profiles, you do not see those options.
• Each input for the Action is displayed as a label/text field with default values pre-filled.
• You can select Cloud Profiles from a drop-down list for each of the steps of the Action (for example, setup, the Action's main step, and cleanup).
• When you switch from Actors to Tags view, a single Actor Tags field displays.

Running Cloud Action Example

Cloud Profile Example

Cloud Action Actor Tags Field

View Job Details

Sample Cloud Job Details

When viewing the Job Details:

• If a Cloud Profile was used, it is displayed at the Action level; if a Cloud Action has multiple scripts, there are multiple Cloud Profiles displayed for the Action.
• If there are inputs, they are displayed at the Action level in the runtime parameters section.
• There is a Cloud Log Output section.
• The Action script can be viewed in the Script Section.
• There is a Cloud Action Output section.
• Errors that are expected from Job results, such as when an Action is blocked with an exception like "UnauthorizedOperation", are captured on the Job Results page.
  

  Job Action error description

• You can view the Job Action error description by clicking the Errored box, as well as view the Cloud log output.
  

  Cloud Log Output

  As an example, a test is written to see if a particular role can create a new user account. At execution, the expected result is that this event is always detected, but whether or not it is blocked is entirely dependent on what role is being tested; an SRE role gives different results than a developer role or a manager role.

Common Issues

These are some of the common issues that may cause you to get an error:

• Failure to build an image (for example, an invalid dockerfile)

• Failure to load an image (for example, corrupt vdockerimage.tar.gz attached)

• Failure to start the container (for example, the specified image doesn't exist)

• Script exceptions

• Script timeouts

• Cleanup script exceptions

• Cleanup script timeouts

• Any errors defined in MSV_ACTION_ERRORS output