-
Notifications
You must be signed in to change notification settings - Fork 511
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
Remove the HTTP endpoint for Notary Signer #870
Remove the HTTP endpoint for Notary Signer #870
Conversation
e2bf987
to
a487935
Compare
👍 Thanks for the ping. It's great to see this |
…ing. This removes the maintenance burden of keeping them in sync. Signed-off-by: Ying Li <[email protected]>
a487935
to
5d6bd65
Compare
localhost only. That means that the server will not be | ||
accessible except locally (via SSH tunnel, or just on a local | ||
terminal)</li> | ||
</ul> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you for updating docs too! 👍
this is awesome, LGTM |
All the LGTMs! |
@endophage is this for v0.4.0? |
@SvenDowideit given it has been merged, yes it will be included in 0.4.0. Note it's only the signer that is losing plain HTTP endpoints, and nobody but the server was talking to the signer (and the server was only using GRPC). |
cool - the docs tooling uses the milestone to determine if a PR should be published, so I've added 0.4 |
Since its' not used by anything. The signer is generally kept hidden in notary service deployments anyway, and the GRPC interface is the main supported interface.
cc @NathanMcCauley
I also wanted to check if anyone was doing anything with the HTTP interface first, though. @andrewhsu @ecordell @HuKeping @mtrmac?