VCS-driven workflow
The HCP Terraform workflow in which a workspace is linked to a repository branch and runs start from commits and pull requests.
In more detail
HCP Terraform registers webhooks with the VCS provider, queues a run when commits land on the tracked branch, and runs speculative plans for pull requests. Pull requests from forks never trigger plans. Trigger patterns can limit runs to changes in chosen paths.
Example
Merge to main queues a run in booking-prodRelated terms
- speculative plan — A plan-only HCP Terraform run that previews changes and can never be applied.
- CLI-driven workflow — The HCP Terraform workflow in which terraform plan and apply, run at a terminal with a cloud block, upload the working directory and run it remotely.
- API-driven workflow — The HCP Terraform workflow in which your own tooling uploads a configuration version and starts runs through the API.
- version control — A system, usually Git, that records every change to a set of files with who made it and why, so work can be reviewed and rolled back.
Taught in
- VCS, CLI And API Workflows: Speculative Plans And Run Triggers — HashiCorp Terraform Associate (004) Exam Prep