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
As part of the upcoming Terraform CLI version 0.15 release, a newer version 6 of the Terraform Plugin Protocol is now available. This protocol bump includes goodies such as NestedType that will benefit the future of plugin development.
Proposal
Begin porting over the existing tfprotov5 directory into a new tfprotov6 directory and perform the protocol additions. If there is any decision making that needs to be made regarding the implementation details, coalesce them onto this issue.
(I don't mind starting this work at some point in the near future as this directly impacts a project I am working on.)
I think we have some ongoing conversations about this with @mildwonkey and it's on our radar.
I currently have the following questions. This is not a complete or exhaustive list:
Should terraform-plugin-sdk get bumped to protocol 6 or remain at protocol 5?
Should we be able to mux between protocol 5 and protocol 6 providers?
Should each protocol version have its own tftypes implementation, or should tftypes be a top-level package that every protocol version depends on?
I don't know that any of these questions has a straightforward answer, and I think all of them will require some discussion because of the implications and nuance.
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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
terraform-plugin-go version
Use cases
As part of the upcoming Terraform CLI version 0.15 release, a newer version 6 of the Terraform Plugin Protocol is now available. This protocol bump includes goodies such as
NestedType
that will benefit the future of plugin development.Proposal
Begin porting over the existing
tfprotov5
directory into a newtfprotov6
directory and perform the protocol additions. If there is any decision making that needs to be made regarding the implementation details, coalesce them onto this issue.(I don't mind starting this work at some point in the near future as this directly impacts a project I am working on.)
References
The text was updated successfully, but these errors were encountered: