run trigger

An HCP Terraform connection that queues a run in a workspace whenever a source workspace applies successfully.

In more detail

A workspace can have up to 20 source workspaces. Runs started by a run trigger do not apply by themselves unless the workspace turns on auto-apply for run triggers, a setting separate from ordinary auto-apply. The target usually reads the source's outputs through a data source once the source shares its state.

Example

network-prod applies, booking-prod queues a run

Related terms

• HCP Terraform workspace — The HCP Terraform container for one collection of infrastructure: its configuration source, variables, state, run history and team access.
• HCP Terraform — HashiCorp's hosted service for running Terraform, which keeps state, runs plans and applies on its own machines, and controls who may change what.

Taught in

• Collaboration And Governance: Teams, Policies, Registry And Health — HashiCorp Terraform Associate (004) Exam Prep
• VCS, CLI And API Workflows: Speculative Plans And Run Triggers — HashiCorp Terraform Associate (004) Exam Prep
• Trap Sprint: Twelve Answers That Are Almost True — HashiCorp Terraform Associate (004) Exam Prep
• The Full Mock: Sixty Minutes, Eight Areas, One Plan For The Last Week — HashiCorp Terraform Associate (004) Exam Prep

References

• HCP Terraform: Run triggers

Certification courses

• Terraform Associate course and practice exam: HashiCorp Terraform Associate (004)