-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Allow removing key from Private
data
#910
Comments
Hey @gdavison 👋 Thank you for raising this and we should certainly support this in some manner. As a workaround for now, does In terms of actual key removal, I think we could support either a new |
Yes, I'm using the
|
Reference: #910 This change ensures that developers can fully remove private state keys by setting the value to `nil` or `[]byte{}`. Attempting to set the value to either value would previously generate an error. The closest available workaround was to set keys to the literal JSON `null` and handle that value during unmarshaling, rather than purely checking existence via `GetKey()` returning `nil`.
#911) Reference: #910 This change ensures that developers can fully remove private state keys by setting the value to `nil` or `[]byte{}`. Attempting to set the value to either value would previously generate an error. The closest available workaround was to set keys to the literal JSON `null` and handle that value during unmarshaling, rather than purely checking existence via `GetKey()` returning `nil`.
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. |
Module version
Use-cases
Resource
Private
data may sometimes no longer be needed. There is currently no way to remove it.Attempted Solutions
Setting a key to
nil
or""
causes an error, such asProposal
Add a corresponding function
RemoveKey
to*privatestate.ProviderData
.The text was updated successfully, but these errors were encountered: