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
Using the TF_LOG_SDK_PROTO_DATA_DIR environment variable, it is possible to output the data being sent between Terraform and providers. This data does not currently include the resource private state, which is managed solely by providers, but must be passed across the protocol to be preserved. It can be helpful to see this data when troubleshooting private state functionality.
Attempted solutions
Viewing private state information via the state file from manual Terraform executions, outside the provider acceptance testing framework.
Proposal
For protocol RPCs that have private state fields, include them in TF_LOG_SDK_PROTO_DATA_DIR output:
If empty, writing a ..._{FIELD}.empty file.
If non-empty, writing the []byte directly to a ..._{FIELD} file.
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
Using the
TF_LOG_SDK_PROTO_DATA_DIR
environment variable, it is possible to output the data being sent between Terraform and providers. This data does not currently include the resource private state, which is managed solely by providers, but must be passed across the protocol to be preserved. It can be helpful to see this data when troubleshooting private state functionality.Attempted solutions
Viewing private state information via the state file from manual Terraform executions, outside the provider acceptance testing framework.
Proposal
For protocol RPCs that have private state fields, include them in
TF_LOG_SDK_PROTO_DATA_DIR
output:..._{FIELD}.empty
file.[]byte
directly to a..._{FIELD}
file.References
The text was updated successfully, but these errors were encountered: