MsgPack encoding issue after upgrading to v0.5.0 #133
Comments
|
Thanks for filing this, @alexsomesan! This certainly feels like a regression. Just noting that #107 would definitely help with troubleshooting here. If I recall from before the end of year break, we saw that msgpack code 84 represents a fixmap (if I'm understanding correctly, with 2 objects) according to the specification. Since Is spinning up a bare bones EKS cluster good enough for executing those examples or is there further testing setup necessary? |
|
@alexsomesan if you could give #135 a try with the |
Reference: #94 Reference: #99 Reference: #100 Reference: #128 Reference: #133 Reverts incorrect logic for handling DynamicPseudoType values in `tftypes`. This type information must be preserved when traversing the protocol, as Terraform CLI decodes values based on the schema information. If a concrete value type is used where DynamicPseudoType is expected, Terraform CLI will return errors such as (given an object of 4 attributes, when DynamicPseudoType is expected): ``` │ Error: ["manifest"]: msgpack: invalid code=84 decoding array length ```
Reference: #94 Reference: #99 Reference: #100 Reference: #128 Reference: #133 Reverts incorrect logic for handling DynamicPseudoType values in `tftypes`. This type information must be preserved when traversing the protocol, as Terraform CLI decodes values based on the schema information. If a concrete value type is used where DynamicPseudoType is expected, Terraform CLI will return errors such as (given an object of 4 attributes, when DynamicPseudoType is expected): ``` │ Error: ["manifest"]: msgpack: invalid code=84 decoding array length ```
|
v0.6.0 was just released 👍 |
|
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-go version
Relevant provider source code
// insert code hereTerraform Configuration Files
# insert config hereExpected Behavior
Provider should work the same as with versions of terraform-plugin-go prior to v0.5.0
Actual Behavior
Steps to Reproduce
Build the Kuberentes provider from the
update-sdkbranch and setup dev overrides for the binary.Run
terraform planin any of the examples for thekubernetes_manifestresource.The issue arises in the Terraform process on the return path from
PlanResourceChangewhen decoding the response value. The issue is present even if no manipulation of the proposed plan is done in the provider (simply looping back the proposed plan).References
The text was updated successfully, but these errors were encountered: