How can you trigger a run in a Terraform Cloud workspace that is connected to a Version Control System (VCS) repository?

How can you trigger a run in a Terraform Cloud workspace that is connected to a Version Control System (VCS) repository?

• A. Only Terraform Cloud organization owners can set workspace variables on VCS connected workspaces
• B. Commit a change to the VCS working directory and branch that the Terraform Cloud workspace is connected to
• C. Only members of a VCS organization can open a pull request against repositories that are connected to Terraform Cloud workspaces
• D. Only Terraform Cloud organization owners can approve plans in VCS connected workspaces

Answer: (B)

When a Terraform Cloud workspace is linked to a VCS repository, runs are triggered by activity in that repository. Specifically, committing and pushing changes to the branch that the workspace is connected to sends a webhook to Terraform Cloud, which then starts a new run using the configuration from that branch. This linkage lets changes in your code automatically trigger planning (and potentially applying) in the cloud, according to the workspace’s run settings. Permissions around setting variables or approving plans don’t control how a run starts; they govern who can perform those actions. Opening a pull request could trigger a run in some setups if the VCS integration is configured to respond to PR events, but the standard and most direct trigger is a commit to the connected branch, which is why committing changes is the correct mechanism.

When a Terraform Cloud workspace is linked to a VCS repository, runs are triggered by activity in that repository. Specifically, committing and pushing changes to the branch that the workspace is connected to sends a webhook to Terraform Cloud, which then starts a new run using the configuration from that branch. This linkage lets changes in your code automatically trigger planning (and potentially applying) in the cloud, according to the workspace’s run settings.

Permissions around setting variables or approving plans don’t control how a run starts; they govern who can perform those actions. Opening a pull request could trigger a run in some setups if the VCS integration is configured to respond to PR events, but the standard and most direct trigger is a commit to the connected branch, which is why committing changes is the correct mechanism.