Config rpc enable flags, fixed logger setup #61
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.
Adds partner_plugin.enabled and rpc_server.enabled config fields/flags. Those bool fields will control if partner plugin rpc client or bot rpc server are started.
Fixes logger setup. Now it will correctly create zap production/development logger according to config developer_mode. Previously it was reading this field before reading config file, so it would use default value in case if it wasn't given as env or flag.