You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently with the new Common Config, the common Host settings, i.e MessageBus.Host, etc., are in common config in the Config Provider. When running from command line in hybrid mode with Config Provider, the common Host settings have been overridden with the docker network names and are not valid when running service outside docker.
The current workaround is to have these common Host settings commented out every services' local private configuration file. When running the service in hybrid mode with Config Provider, the developer must uncomment these settings.
🚀 Feature Request
Relevant Package [REQUIRED]
This feature request is for C Device SDKDescription [REQUIRED]
Currently with the new Common Config, the common
Host
settings, i.e MessageBus.Host, etc., are in common config in the Config Provider. When running from command line in hybrid mode with Config Provider, the commonHost
settings have been overridden with the docker network names and are not valid when running service outside docker.The current workaround is to have these common Host settings commented out every services' local private configuration file. When running the service in hybrid mode with Config Provider, the developer must uncomment these settings.
ref:
Describe the solution you'd like
Add the new
-d/--dev
command flag which will cause all the Host settings pulled from common configuration to be overridden with the valuelocalhost
.Refer to these PRs in Go:
Describe alternatives you've considered
Use current work around of commented out settings which clutter the service config files
The text was updated successfully, but these errors were encountered: