go/runtime: Add key manager EnclaveRPC support to client runtime hosts #4244
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 runtimes hosted on client nodes were not able to issue EnclaveRPC
requests as the endpoint was not implemented in the handler. This unifies the
handler implementations between the client and compute nodes and makes sure that
key manager requests are possible (of course client nodes will only be able to
request public keys).
Also removes the EnclaveRPC client interface as the idea is to go through runtime
queries (as the SDK now supports using the key manager). Note that the client part
of EnclaveRPC transport was already removed when doing the gRPC refactor.