You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of letting our users discover and report such cases of false diagnostics we can be more proactive and run our validation logic against publicly available repositories of Terraform code on GitHub, to perform a form of smoke testing of the validation logic.
This can in turn provide us with higher confidence in the validation logic and the schema, and detect at least some, if not most, of the bugs before they even reach users.
Identify some popular repositories with Terraform code on GitHub and the Terraform Registry
Create a script (Go code) which can run all existing validation logic
Context
After introducing enhanced validation in #1368 we have received a number of bug reports about false diagnostics:
for_each
hcl-lang#333terraform_remote_state
data source terraform-schema#272cloud
organization
optional terraform-schema#271DefaultValue
for relevant attributes terraform-schema#270connection
terraform-schema#269target_platform
is recognised in nestedconnection
block terraform-schema#268and some more continue to trickle in:
config
attribute not expected interraform_remote_state
data source vscode-terraform#1606Proposal
Instead of letting our users discover and report such cases of false diagnostics we can be more proactive and run our validation logic against publicly available repositories of Terraform code on GitHub, to perform a form of smoke testing of the validation logic.
This can in turn provide us with higher confidence in the validation logic and the schema, and detect at least some, if not most, of the bugs before they even reach users.
SchemaModuleValidation
,SchemaVariablesValidation
)ReferenceValidation
)The text was updated successfully, but these errors were encountered: