internal/privatestate: Handle terraform-plugin-sdk private state in NewData #452
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ewData
Previously, errors such as these could be returned:
```
Error: Error Decoding Private State
with random_password.min,
on terraform_plugin_test.tf line 1, in resource "random_password" "min":
1: resource "random_password" "min" {
An error was encountered when decoding private state: illegal base64 data at
input byte 0.
This is always a problem with Terraform or terraform-plugin-framework. Please
report this to the provider developer.
```
The new unit test case would fail with the same error prior to this fix.
1 task
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, errors such as these could be returned:
The new unit test case would fail with the same error prior to this fix.