Runs Tab

The Runs tab lists all workflow executions (runs) and their statuses.

Runs list

Displays a list of all workflow runs.

Each run entry shows:

• Run ID and trigger source (manual, scheduled, API)
• Latest status (Queued, Pending, In Progress, Running, Succeeded, Failed )
• Context tags
• Created by
• Modified at
• Source
• Approval detail

You can search by name and filter or sort runs by actions, status and context tags. You can also cancel the active runs by clicking the red button in the Latest status column.

Runs list

Run details view

Selecting a run ID opens the run details page. The header shows the run ID, a summary of resource changes, and the following metadata:

• Status
• Action
• Terraform version
• Source
• Created at
• Duration
• Contextual Tags To return to the runs list, select ← All runs. To open the previous modal-based view, select Open previous view in the top-right corner.

The run details page has three tabs: Summary, Parameters, and Logs.

Summary

The Summary tab gives you a structured overview of the run. It contains the following collapsible sections:

Summary tab

Trigger details

Shows how the run was triggered, including the timestamp, action type, and source repository.

Inputs

Appears when input variables were configured for the run. Shows each input key and the value passed at the time the run was triggered.

Inputs

Plan

Shows the number of resources the run adds, changes, and destroys, along with a timestamp for when the plan ran. Select View plan logs to open the Logs tab for this run.

Expand the Plan section to see:

• Resources list — shows each resource's type, name, and provider. Use the search field to find a specific resource, the Operations filter to narrow results by operation type, and Columns to choose which columns are visible.
• Outputs — lists each output key, its type, and its value. Values for resources that haven't been created yet show as (known after apply).

Plan section

Infracost estimation

Shows the estimated hourly and monthly cost of the resources in the plan, the total number of usage-based resources, and a percentage change compared to the last applied run. A breakdown by resource is available below, showing each resource's address, service, type, and estimated hourly and monthly cost.

Infracost estimation

Policy checks

Shows the result of every policy rule evaluated against the run. The policy overview bar displays a count for each result type: Pass, Warn, Fail, Pending Approval, and Skip.

Each row in the list shows the rule name, result, policy tool, and policy name. Select View policy evaluation to open a detailed breakdown of a specific rule, including the Tirith Evaluation Expression, its ID, description, whether it passed, and the evaluation result. A JSON View toggle is available for the full raw output.

Policy checks

Policy evaluation modal

Approval required

Appears when the run requires approval before proceeding. Select Review & Approve to review the workflow configuration and approve or reject the run.

Apply / Destroy

Appears once the plan has been approved and the apply or destroy step has run or is pending. Shows the status of the step and a link to view the apply logs.

Expand the section to see:

• Resources list — shows each resource's type, name, and provider. Use the search field to find a specific resource, the Operations filter to narrow results by operation type, and Columns to choose which columns are visible.
• Outputs — lists each output key, its type, and its value.

note

This section appears as Apply when the action is Create, and as Destroy when the action is Destroy.

Workflow steps

Appears when custom workflow steps were configured for the run. Steps are grouped by execution phase, such as pre-plan, pre-apply, or post-apply, and show the status of each step. Only the phases configured for that specific run are shown.

Workflow triggers

Appears when workflow triggers were configured at the time of the run. Shows each trigger type, such as Workflow chaining, Webhook, or Email, along with the condition that was evaluated and whether it was met. The section header shows a summary count of triggered and not triggered results.

Select View trigger settings on any trigger to open its configuration. Select View all to see all entries for triggers with multiple configured actions.

Workflow triggers

note

For custom workflow types such as CloudFormation or Ansible, the Plan and Apply sections are not available. The Summary tab shows only the workflow steps configured for that run.

Parameters

Shows the workflow parameters used for this run in JSON format. Toggle Compare mode to diff the parameters of this run against another run. When enabled, the view splits into two panels, the current run on the left and the selected run on the right, with differences highlighted. Use the Split and Unified toggles to switch between diff views.

Parameters tab — Compare mode

Logs

Shows the full log output for the run, grouped into collapsible accordion sections by workflow step. Use the search field to find specific log lines. Select Collapse all to collapse all sections at once. Select the settings icon to access log display options:

• Show timestamps — toggle timestamps on or off for each log line.
• Download raw logs — download the full log output as a file.
• View raw logs — open the full log output in a new browser tab, without accordion grouping.

Logs tab

Accessing workflow files

StackGuardian simplifies accessing and working with workflow files by providing a dedicated workspace for users to manage their workflow runs. Below are the file paths and directories available within the user's workspace for running their workflows:

Mount Workflow Files in Workflow Steps

1. Root Directory: /mnt/sg_workspace

   • This serves as the starting point for accessing all workflow files.

2. Workflow Steps Directory:

   • Path: /mnt/sg_workspace/user/{repository-name}
   • This directory contains the version control system (VCS) repository, named after the repository's name, and includes all the files from the user's repository.
   • Note: A tfplan.json file is also available in this directory after the Terraform plan step completes. This file is accessible both pre-apply and post-apply.

   Example:
   /mnt/sg_workspace/user/template-tf-aws-s3-demo-website/tfplan.json

3. Artifacts directory:

   • This directory stores all the artifacts generated by the workflow steps. It is crucial for accessing any outputs or logs produced during the workflow run.

Understanding these file paths and directories helps users customize or further process files within the Terraform workflow. It provides a clear structure for accessing and managing files throughout the workflow run.

Private module VCS Auth in workflows

In order to fetch private modules from version control repositories, you can authenticate correctly using the following ways:

• Integration: StackGuardian integrates with Bitbucket, Azure DevOps, and GitHub. When creating a workflow, you provide the repository URL and credentials within the VCS settings. If your repository is private, StackGuardian uses these credentials to fetch the required code during workflow runs.

• Secrets: Optionally, you can use secrets to manage your authentication credentials. Create a secret with the format username:password or just the password, where the default username is x-access-token. Secrets provide a more secure way to store sensitive information.

Fetching private modules

When utilizing private modules in your workflow, follow this format for your module block:

module "vpc" {
  source = "git::https://example.com/vpc.git"
}

note

Ensure that the repository URL is in the HTTPS format as shown above. It's common to mistakenly use the generic Git repository URL, which might not work as expected.