TA-002-P · Question #336
In a Terraform Cloud workspace linked to a version control repository, speculative plan runs start automatically when you merge or commit changes to version control.
The correct answer is B. False. In Terraform Cloud, speculative plan runs are triggered by pull requests (PRs) or merge requests, not typically by direct merges or commits to the main branch. Commits and merges to the main branch usually trigger a full apply run if configured, not a speculative plan.
Question
In a Terraform Cloud workspace linked to a version control repository, speculative plan runs start automatically when you merge or commit changes to version control.
Options
- ATrue
- BFalse
How the community answered
(19 responses)- A11% (2)
- B89% (17)
Why each option
In Terraform Cloud, speculative plan runs are triggered by pull requests (PRs) or merge requests, not typically by direct merges or commits to the main branch. Commits and merges to the main branch usually trigger a *full apply run* if configured, not a speculative plan.
Speculative plans are designed for pull/merge requests to preview changes before merging, while merges/commits to the main branch typically trigger full runs, not speculative plans.
Speculative plans in Terraform Cloud are primarily triggered by opening, updating, or commenting on a pull request (or merge request), allowing you to review the proposed infrastructure changes before they are merged into the main branch. Direct commits or merges to the configured branch (e.g., `main` or `master`) usually initiate a standard "apply" run, not a speculative plan.
Concept tested: Terraform Cloud speculative plans
Source: https://developer.hashicorp.com/terraform/cloud/run/speculative-plans
Topics
Community Discussion
No community discussion yet for this question.