Runs Tab

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

---

1. 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.

2. Run Details View

Clicking a workflow run id opens a detailed execution view that includes:

• Logs
• Errors
• Compare parameters
• Parameters
• Compliance Checks
• Infracost Estimation
• Plan
• Provisioned Resources
• Comments

This section helps users analyze executions, review outcomes and troubleshoot issues effectively.

3. Accessing Workflow Files in StackGuardian

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.

4. Private Module VCS Auth in Workflows

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

1. 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.

2. 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.