8.2.2. Collaboration Features
💡 First Principle: Collaboration features turn infrastructure runs into a shared, governed team process — with version-control integration, review steps, cross-workspace visibility, and continuous health checks — so the platform supports many engineers safely working on shared infrastructure.
HCP Terraform's collaboration capabilities the exam may reference: VCS integration (connect a Git repository so commits trigger runs and PRs show plan output), change requests (a backlog of action items recorded on a workspace, such as a module upgrade or security fix, that notifies the owning team — not an approval gate), the Explorer (query and report across all workspaces in an organization), health assessments (continuous drift detection and continuous validation of your infrastructure against config), teams (role-based access control for who can do what), and the private module registry for sharing internal modules.
⚠️ Exam Trap: Health assessments are how HCP Terraform performs drift detection and continuous validation automatically — distinct from running plan -refresh-only yourself in the CLI. And the Explorer is for cross-workspace visibility/reporting, not for editing infrastructure.
Reflection Question: How does HCP Terraform's health-assessment drift detection differ operationally from the manual apply -refresh-only approach you learned in Phase 6?
