Skip to content
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

Support ProxyGatewayEndpoint from legacy configuration #5214

Merged
merged 2 commits into from
Dec 11, 2018

Conversation

ReubenBond
Copy link
Member

@ReubenBond ReubenBond commented Dec 4, 2018

Propagates the ProxyGatewayEndpoint setting from legacy NodeConfiguration to EndpointOptions. The silo-to-silo endpoint options are being propagated correctly and don't need to change.

GatewayPort is redundant and should not be used if GatewayEndpoint is set, but it shouldn't hurt to explicitly set it anyway. EDIT: setting gateway port here GatewayPort wasn't redundant: it was being used to determine whether or not to start a gateway, etc. I added changes to fix that.

@ReubenBond
Copy link
Member Author

@dotnet-bot test functional

Opened #5215 for the initial failure

@ReubenBond ReubenBond force-pushed the fix-legacy-gateway-config branch from 0ec9ecd to 48493d3 Compare December 5, 2018 19:32
@sergeybykov sergeybykov merged commit 3ad669b into dotnet:master Dec 11, 2018
@ReubenBond ReubenBond deleted the fix-legacy-gateway-config branch December 11, 2018 17:09
sergeybykov pushed a commit to sergeybykov/orleans that referenced this pull request Dec 11, 2018
@github-actions github-actions bot locked and limited conversation to collaborators Dec 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants