fix: expose private API on private port #9
Merged
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.
Because
This commit
Notes
Other services listen and serve both the public and the private API through the grpc-gateway. In the case of this service this isn't needed for the private API as it doesn't expose any HTTP endpoints (other services don't need to, either, but it's already exposed). Therefore, the "listen and serve" strategy is a bit different. The gRPC config should already contain the TLS information, if present, so we don't need an if/else block for the private API.