Terraform Provider Version Pinning Language Collocations
Practise the standard verbs for pinning terraform provider versions safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ every provider version in the required_providers block so an unexpected major upgrade never breaks a plan.'
We 'pin a version' — the standard, established terraform collocation for locking a provider to a specific release. The other options aren't the recognised term here.
2 / 5
Fill in: 'Leaving a provider constraint unbounded can ___ a routine terraform init pulling in a breaking new major version.'
We say an open constraint will 'allow' a breaking upgrade — the standard, natural collocation for the resulting risk. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the lock file into version control so every teammate resolves the exact same provider version.'
We 'commit' a file — the standard, simple collocation for adding a file to source control. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ provider upgrades in a dedicated pull request so the diff isn't buried inside an unrelated infrastructure change.'
We 'isolate' an upgrade — the standard collocation for separating a change into its own reviewable unit. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ the changelog for every provider bump so a silently deprecated resource argument doesn't surprise us in production.'
We 'review' a changelog — the standard, simple collocation for reading release notes before adopting a change. The other options are less idiomatic here.