Closed theory closed 1 year ago
In Java, we now have a new API to edit KeysetHandles, namely the KeysetHandle.Builder. We want to move away from the KeysetManager.
In golang, we don't yet have this new API, but eventually we also want to move away from keyset.Manager. So we prefer to not put any additional work into this API.
Why do you need Destroy? Couldn't you use Delete instead?
I only noted it here because it was missing and therefore diverged from the docs. I don't use it.
Ok, thanks. Which docs are you referring to? If the documentation says something different than the code then we should update the documentation.
Oh, maybe I didn't see it in the docs, but in the tinkey CLI:
❯ tinkey
Argument wrong!
org.kohsuke.args4j.CmdLineException: Argument "command" is required
[add-key | convert-keyset | : Command to run
create-keyset | create-public-keyset
| delete-key | destroy-key |
disable-key | enable-key |
list-keyset | list-key-templates |
rotate-keyset | promote-key]
I was implementing a tinkey-like CLI so was looking for completeness. I do use use delete, and honestly wasn't sure what the difference was supposed to be.
Thanks for filing this, but we believe this whole DESTROYED thing is rather confusing. We will probably solve this differently and most likely remove "destroyed". I will close this.
Should there be a Destory method on the Go manager? Something like: