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
An issue describing that Planned value does not match config value for number on Terraform core has resulted in a fix in cty in v1.14.4 (refer to hashicorp/terraform#34866 (comment)). The fix was to change the MessagePack encoder to use a different encoding for large integers. This should fix the core-to-provider direction in terraform-plugin-go, but equivalent changes will need to implemented in this repository for the provider-to-core direction.
The changes to Terraform core and terraform-plugin-go should be coordinated to minimise any time during which encodings differ for Terraform core and terraform-plugin-go.
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
An issue describing that Planned value does not match config value for number on Terraform core has resulted in a fix in cty in v1.14.4 (refer to hashicorp/terraform#34866 (comment)). The fix was to change the MessagePack encoder to use a different encoding for large integers. This should fix the core-to-provider direction in terraform-plugin-go, but equivalent changes will need to implemented in this repository for the provider-to-core direction.
The changes to Terraform core and terraform-plugin-go should be coordinated to minimise any time during which encodings differ for Terraform core and terraform-plugin-go.
References
The text was updated successfully, but these errors were encountered: