chore(local dev): Allow for custom GRPC port to be specified #100231
Closed
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.
I and some other coworkers had an issue where colima was using port 50051, which is the port that taskbroker also wants to use. Changing the port that taskbroker uses caused tasks to start flowing again
This is an attempt to use port 50055 solely in the devservices/local development environment
corresponding taskbroker PR: getsentry/taskbroker#492