-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catch panics when typechecking warns #1987
Labels
kind/enhancement
Improvements or new features
Comments
iwahbe
added
needs-triage
Needs attention from the triage team
kind/enhancement
Improvements or new features
labels
May 17, 2024
corymhall
added a commit
that referenced
this issue
May 20, 2024
The type checker is meant to catch user configuration errors that would eventually cause a panic. We are currently only logging a warning so we are not preventing the panic from happening. Even though we have the additional warning, it is still confusing to users and some do not correlate the warning with the panic. This PR catches the panic when we do have type errors so that the user will only see the warning and not the panic. closes #1987
corymhall
added a commit
that referenced
this issue
May 23, 2024
The type checker is meant to catch user configuration errors that would eventually cause a panic. We are currently only logging a warning so we are not preventing the panic from happening. Even though we have the additional warning, it is still confusing to users and some do not correlate the warning with the panic. This PR catches the panic when we do have type errors so that the user will only see the warning and not the panic. closes #1987
VenelinMartinov
added a commit
to pulumi/pulumi-gcp
that referenced
this issue
Sep 17, 2024
This adds a regression test for the warnings we issue to users when a property has the wrong type. This could result in panics down the line, so we need to catch them early. Testing this in the bridge is currently quite hard as we can't use YAML for this because it is too strict in type-checking. We only have unit tests which indirectly test this but these break under PRC. This was introduced in pulumi/pulumi-terraform-bridge#1987 original GCP issue: pulumi/pulumi-terraform-bridge#1979 Bridge issue for integration tests for the feature: pulumi/pulumi-terraform-bridge#2418
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
Issue details
Terraform providers are not expected (and do not) handle mistyped input. They often panic on mistypes inputs. When the typechecker fails, we knowingly feed them mistyped input. As long as we continue this practice, we should
recover()
from upstream panics when there were type checker failures.This would reduce the impact and improve the error message when types don't line up: helping users to find and address the underlying issue faster and improving confidence in the bridge.
Follow up on #1979.
Affected area/feature
The text was updated successfully, but these errors were encountered: