Terraform Associate 004 ยท HCP Terraform
Collaboration features in HCP Terraform
Teams and permissions, run approval and comments, private registry, remote state sharing, notifications (8b).
Key points
- Users join teams, and teams get permissions at organization, project or workspace scope.
- Permissions are additive: the highest level granted anywhere wins.
- Runs can pause for approval and carry comments, the private registry shares modules and providers inside the organization, and notifications tell people about run events.
Source: https://developer.hashicorp.com/terraform/cloud-docs/users-teams-organizations/permissions
Practice questions
To whom do you normally grant permissions in HCP Terraform?
- To teams that users belong to
- To individual provider plugins
- To cloud regions
- To state file names
Show answer
Answer: A. To teams that users belong to
Users are added to teams, and the teams receive permissions. Granting per individual or per cloud region is not the model.
Which statements about the private registry are correct?
- It can hold private modules
- It can hold private providers
- Its private content is visible only to members of the owning organization
- Anyone on the internet can install its private modules
- It can only store modules written in Python
Show answer
Answer: A. It can hold private modules, B. It can hold private providers, C. Its private content is visible only to members of the owning organization
The private registry hosts private modules and providers visible only to the owning organization, and it can also list public ones synced from the public registry. It is not a public marketplace.
If a team has a high permission at organization level and a lower role on one workspace, the lower role overrides it on that workspace.
Show answer
Answer: False
False. Permissions are additive, so the highest level granted at any scope applies.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
