Collaborate on infrastructure as code using HCP Terraform1 / 5
An HCP Terraform workspace is connected to a VCS repository with `Branch: main` and `Working Directory: infra/`. Which event automatically queues a plan?
CorrectNot quite
Alex
VCS-driven HCP Terraform workspaces register webhooks and queue runs only when commits land on the configured branch and modify files within the configured working directory. With Branch: main and Working Directory: infra/, only commits to main touching infra/ trigger a plan. The option “Any commit to any branch of the connected repository” ignores both branch and directory filters. The option “Commits whose message contains "[apply]" or "[plan]"” describes a commit-message convention HCP Terraform does not support. The option “A pull request opened against any branch of the repo” confuses speculative plans (triggered by PRs) with the auto-queued plan behavior tied to branch commits. Ref: developer.hashicorp.com/terraform/cloud-docs/workspaces/settings; /terraform/cloud-docs/workspaces/run/ui
Sourcedeveloper.hashicorp.com
Create a free account to keep asking Alex — no credit card required.
Question 1 of 5
Get started free