API-driven workflow
The HCP Terraform workflow in which your own tooling uploads a configuration version and starts runs through the API.
In more detail
The tooling packs the configuration directory as a tar.gz file with the configuration at its root, creates a configuration version, and uploads the archive. The upload queues a run, which the tooling can poll and apply. It suits pipelines and version control systems HCP Terraform does not support directly.
Example
tar -czf config.tar.gz -C booking .Related terms
- configuration version — One uploaded snapshot of a workspace's Terraform configuration that HCP Terraform runs against.
- 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.
- 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.
Taught in
- VCS, CLI And API Workflows: Speculative Plans And Run Triggers — HashiCorp Terraform Associate (004) Exam Prep