-
Notifications
You must be signed in to change notification settings - Fork 14
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
Migration to terraform-plugin-testing
causes panic in existing test suite
#93
Comments
Hi @jacobbednarz 👋 Sorry you ran into trouble here. The panic suggests that the
The After cloning and checking out cloudflare/terraform-provider-cloudflare#2272 a search for
Can you check that all of the required updates when switching to using |
thanks for the pointer @bendbennett. the migration guide only calls out swapping test files ( |
@jacobbednarz you are quite right. The migration guide only refers to |
appreciate it! 🙇 |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
terraform-plugin-testing version
Relevant provider source code
// n/a
Terraform Configuration Files
// n/a
Expected Behavior
This is reproducible by checking out the
master
branch that has not migrated to the terraform-plugin-testing repository and still uses the SDKv2 references.Actual Behavior
Steps to Reproduce
make test
References
I'm not seeing any differences between sdkv2 (https://github.com/hashicorp/terraform-plugin-sdk/blob/main/helper/resource/testing.go#L48) and this repository (https://github.com/hashicorp/terraform-plugin-testing/blob/main/helper/resource/testing.go#L53) that would be causing this. I suspect it may be a bug in either my find and replace that was done as part of the migration or a bug in our existing test suite that we are now privvy to but would love some guidance on where to start with this one.
I've tried running this one through git bisect to see where it's falling apart but the cross repository interactions and merging is making it a little tough without more understanding of where I should focus my effort.
The text was updated successfully, but these errors were encountered: