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
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
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.
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
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
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: