-
Notifications
You must be signed in to change notification settings - Fork 214
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
[Merged by Bors] - node: Remove option to configure services per endpoint #5276
Conversation
in reality none of them can be exposed on internet facing public address. |
I wanted to avoid breaking backwards compatibility. At the moment they are all exposed by default. How do you suggest to proceed? |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #5276 +/- ##
=======================================
Coverage 77.5% 77.6%
=======================================
Files 251 251
Lines 29494 29477 -17
=======================================
+ Hits 22873 22878 +5
+ Misses 5172 5155 -17
+ Partials 1449 1444 -5 ☔ View full report in Codecov by Sentry. |
i don't know honestly. any solution seems sketchy. i don't mind doing what you suggested if it works for smapp. |
bors try |
tryBuild failed: |
bors try |
tryBuild failed: |
bors try |
tryBuild succeeded: |
bors merge |
## Motivation Part of #5267 Closes #5260 This changes the node configuration to not allow an operator to decide any more which GRPC handlers are exposed on which endpoint. Instead it hard codes the following: - public: GlobalState, Mesh, Transaction, Node, Activation - private: Admin, Debug, Smesher, Post - mTLS: Post Additionally it removes all configuration options for the PoST service and sets them automatically if the node is started with `smeshing-start=true` via the command line or via the config. ## Changes - remove ability to set which handlers are available on which endpoint and hardcode them instead - remove workaround code added in #5259 that was necessary when the operator could still configure the supervised post service - supervised post service binary is now always expected to be in the same directory as the node binary - the supervised post service is now instructed to always connect to the node via the private listener - remote post services can connect via the TLS listener ## Test Plan updated existing tests ## TODO <!-- This section should be removed when all items are complete --> - [x] Explain motivation or link existing issue(s) - [x] Test changes and document test plan - [x] Update documentation as needed - [x] Update [changelog](../CHANGELOG.md) as needed
Pull request successfully merged into develop. Build succeeded: |
Motivation
Part of #5267
Closes #5260
This changes the node configuration to not allow an operator to decide any more which GRPC handlers are exposed on which endpoint. Instead it hard codes the following:
Additionally it removes all configuration options for the PoST service and sets them automatically if the node is started with
smeshing-start=true
via the command line or via the config.Changes
Test Plan
updated existing tests
TODO