VCS Connected Workspaces Fail to Trigger a Run When a Pull Request is Initiated

Configuration

• A VCS connection to a Terraform Cloud/Enterprise workspace.
• The Terraform Working Directory is set to "/".
• Only trigger runs when files in specified paths changes is enabled and set to "/".
• The workspace is configured to point to a VCS branch.

Problem

A Terraform Cloud / Enterprise workspace can fail to trigger a run when a Pull Request is initiated from the VCS associated repository such as Bitbucket. The webhook fires successfully but no run is triggered in the Terraform Cloud/Enterprise workspace. 

The tfe-sidekiq (ptfe_sidekiq on older Terraform Enterprise versions) container logs will report the following:

[WARN] {:msg=>"No matching ingress triggers", :vcs_repo_id=>"vcrepo-<ID>", :webhook_payload_id=>3968}

Cause

Terraform Cloud / Enterprise workspace already defaults to the root of the repository so manually setting "/" in the Terraform Working Directory is not an expected path setting.

Solutions

To define the root of your repository follow these steps to allow the system to default to it.  

1. Modify the Terraform Cloud / Enterprise Workspace under Settings > General Settings >  Terraform Working Directoryand leave it blank or undefined to allow the system to default to the root of your repository.
2. Within the similar path of the Terraform Cloud / Enterprise Workspace, under Settings > Version Control ensure the Automatic Run Triggering setting for Only trigger runs when files in specified paths changes is not enabled and not configured with "/". 
3. Save the changes and try a pull request from the VCS repository to see if a run is triggered in the Terraform Cloud / Enterprise Workspace. 

Additional Information

• For additional assistance please contact HashiCorp Support to request additional assistance.