fix(terraform_providers_lock
): Require terraform init
(and terraform_validate
hook) run when only lockfile changed
#649
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Put an
x
into the box if that apply:Description of your changes
When the terraform root module contains any child module it requires
terraform init
to run to be able to successfully run the provider lock operation.Previously,
terraform init
was interraform_providers_lock
hook too, but moved out to be only interraform_validate
, because there was little sense to try to lock anything that was code invalid.If we return
terraform init
back toterraform_providers_lock
- major changes in providers that remove resources etc. can be successfully written to lockfile without any checks, as such checks done interraform_validate
Workaround till the release of that stuff
Add
files: (\.tf|\.tfvars|\.terraform\.lock\.hcl)$
toterraform_validate
hook call