Integration of Terraform Cloud with VMware Aria Automation (vRA) using a local execution mode, resulting in a "Bad Gateway" error

Products

• VMware Aria Suite

Issue/Introduction

• Attempted to integrate Terraform Cloud with VMware Aria Automation (vRA) using a local execution mode, resulting in a "Bad Gateway" error during Terraform apply.
• Direct API calls to vRA using the provided refresh token were successful, indicating connectivity from the client to vRA.
• The error appeared during the Terraform apply, specifically at the step where the Terraform CLI communicates with vRA.

Environment

• VMware Aria Automation 8.x

Cause

• The "Bad Gateway" error was caused by the client's use of a proxy to communicate with the internal vRA endpoint, which was not intended for internal connections.
• The NO_PROXY setting did not initially include exceptions for the internal domains, causing internal requests to be routed incorrectly through the proxy.

Resolution

• Update the proxy configuration to include exceptions for internal domains and Set the NO_PROXY environment variable to include .local, .localdomain, localhost, and .company.com
• Adding the internal domains to the NO_PROXY the variable allows direct communication from the client to the vRA server without the proxy interfering hence resolving the "Bad Gateway" error and allowing successful deployment of virtual machines to vRA from the Terraform Cloud.