-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Custom provider built with terraform-plugin-framework does not find resource/data source types with TF 1.6 #33990
Comments
Hi @dhohengassner, Thanks for filing the issue. I think we're going to need a more complete example to figure out what might be going on here. The provider is what is returning the error message, so it's not clear yet what Terraform could be doing differently to cause it. It looks like you have obfuscated the output a bit, but if the provider is called |
Hey @jbardin, Thanks for the quick response and sorry for not mentioning the adjustments earlier. Yeah, you are right; I obfuscated the resource name as well as the output (and not even well 👎 ) since it is an internal provider not meant for public use. The resource/provider names are the only thing I adjusted; the rest of the output comes from an actual pipeline. I'm also curious if other providers using the framework will run into the same issue. |
I haven't heard of anything similar with the framework, and haven't come up with any hypotheses yet about what could be happening either. Are you on the latest release of the framework? If it's possible to put together a minimal config, and a full trace log from the plan, that may help pinpoint what is going on. |
I can replicated this with 1.6.0-beta2 and later by using the data source from https://github.com/hashicorp/terraform-provider-scaffolding-framework without change. |
We're seeing the same issue with both our public provider and a private, internal-use-only, provider. |
Thanks @andrewesweet, the scaffolding example should work as a good starting point! |
Hi all, Detailed investigation of this one is still ongoing, but based on internal discussion it seems like this is a bug in the plugin framework itself but it appears as new in Terraform v1.6.0 because this new Terraform Core release introduced a new provider protocol feature which the framework is attempting to use but is using it incorrectly, causing this error. Based on the information in the framework's changelog it seems like building your providers using framework release v1.3.5 should avoid this problem for now, since the problematic use of the new protocol feature came in v1.4.0. There are folks on the framework dev team digging deeper into this currently, and hopefully we'll have a fix coming soon. The fix is likely to be in the framework primarily, and so will probably require upgrading to a newer version of the framework once fixed, but I'll let the folks working on it share more information about what's required once the details are clearer. Thanks again for reporting this! |
Hi all 👋🏻 , I've opened a bug report for further tracking of this issue: hashicorp/terraform-plugin-framework#853 Also wanted to add that if you downgrade go get -u github.com/hashicorp/[email protected]
go get -u github.com/hashicorp/[email protected] |
Hello, Since there's not going to be any associated change in core to fix the errors here, I'm going to close this issue. Interested parties can follow hashicorp/terraform-plugin-framework#853 for a resolution in the plugin-framework. Thanks! |
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 Version
Terraform Configuration Files
Debug Output
Expected Behavior
Provider works fine as it does with Terraform v1.5
Actual Behavior
The same provider binary crashes with errors:
Steps to Reproduce
terraform init
terraform apply
Additional Context
The provider was built this year on top of the latest framework.
https://github.com/hashicorp/terraform-plugin-framework
References
No response
The text was updated successfully, but these errors were encountered: