-
-
Notifications
You must be signed in to change notification settings - Fork 423
[breaking] Remove ip
flag from daemon command
#2045
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
[breaking] Remove ip
flag from daemon command
#2045
Conversation
Codecov ReportBase: 36.55% // Head: 36.56% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@ ## master #2045 +/- ## ========================================== + Coverage 36.55% 36.56% +0.01% ========================================== Files 229 229 Lines 19383 19383 ========================================== + Hits 7085 7088 +3 + Misses 11462 11460 -2 + Partials 836 835 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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.
Since this is a breaking change UPGRADING.md needs to be updates accordingly
bf9b98a
to
741e065
Compare
ip
flag from daemon command (削除ここまで)ip
flag from daemon command (追記ここまで)
741e065
to
c829944
Compare
Uh oh!
There was an error while loading. Please reload this page.
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)What kind of change does this PR introduce?
Code security improvement
What is the current behavior?
It is currently possible to use
--ip
to set a custom ip for listening to gRPC request.What is the new behavior?
The
--ip
flag is removed and the default value is set to127.0.0.1
.Does this PR introduce a breaking change, and is titled accordingly?
Yes