Fix: run terraform validate
on modules again (Cherry-pick of #20230)
#20299
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.
Only running
terraform validate
on deployments is unexpected for users. See #20222 . Runningterraform validate
on all modules might lead to errors with Terraform, but those are predictable and understandable by users.This MR:
terraform validate
onterraform_modules
againskip_terraform_validate
field forterraform_modules
which cannot bevalidate
d by TerraformIt leaves open the possibility of validating both
terraform_deployment
s andterraform_module
s. Hopefully we can work out something like the Helm backend's handling of kubeconform.