-
Notifications
You must be signed in to change notification settings - Fork 73
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
rework configuration file to deal with telemetry #940
Conversation
@@ -57,6 +57,7 @@ services: | |||
ports: | |||
- "6831:6831/udp" | |||
- "16686:16686" | |||
- "16685:16685" |
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.
nit: you don't need to expose ports for them to work internally
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.
Yeah, but I usually use the to debug the application as well.
@@ -95,6 +96,8 @@ services: | |||
JAEGER_HOST: jaeger | |||
JAEGER_PORT: 6832 | |||
NPM_RUN_COMMAND: api | |||
ports: | |||
- "8081:8081" |
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.
same here
I'm merging it. The front-end tests are failing regardless of the changes we are making. |
This PR reworks how we define telemetry configuration in the config file.
Checklist