Aria Automation: "No terraform path found" for "Source Directory" in Terraform Blueprint Creation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When attempting to create a new Terraform-based blueprint in Aria Automation Assembler after configuring a GitHub integration, users may encounter "No terraform path found" and find the "Source Directory" dropdown to be empty. This typically indicates a misconfiguration in how the GitHub integration.

Example :

Environment

• VMware Aria Automation (all 8.x versions)
• GitHub Integration
• Terraform Content Management in Assembler

Cause

The "Source Directory" dropdown in Aria Automation Assembler pulls its content from the paths configured within the GitHub integration.

Resolution

To resolve this issue, you must review and correct the configuration of your GitHub integration within Aria Automation to ensure it points to the correct location of your Terraform files.

Procedure:

1. Verify GitHub Integration in Aria Automation:

   • Log in to VMware Aria Automation.
   • Navigate to Assembler > Infrastructure > Integrations.
   • Locate and edit your existing GitHub integration.

2. Configure the Project got "Terraform Configurations" Path:

   • Within the GitHub integration settings, ensure that the path specified under "Terraform Configurations" points to the main folder in your Git repository where your Terraform configuration files (e.g., .tf files) reside.

   • Recommendation: Typically, this should be set to / (a single forward slash), indicating the root of your Git repository, this will allow to select all folders inside the GITHUB during the Terraform Templates generation.