Skip to content
This repository was archived by the owner on May 14, 2026. It is now read-only.
This repository was archived by the owner on May 14, 2026. It is now read-only.

Investigate the impact of changing ClientConext's getEndpoint() on downstream Handwritten Libraries #2295

Description

@lqiu96

Modifying this value:

to be the resolved endpoint from the EndpointContext may break downstream handwritten libraries.

If there is no impact, try to change the value.
If there is impact and ClientContext needs to return the resolvedEndpoint, look into exposing a few field to return

Activity

added
type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
priority: p3Desirable enhancement or fix. May not be included in next release.
on Dec 8, 2023

lqiu96 commented on May 21, 2024

@lqiu96
MemberAuthor

ClientContext's getEndpoint() returns the StubSettings' getEndpoint() value which is the resolved endpoint. When data is passed between ClientContext and StubSettings, all the the endpoint information is passed between the two. StubSettings will recreated the EndpointContext with the original values so any user configurations will not be lost.

Going to close this issue as this was done in #2715

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: p3Desirable enhancement or fix. May not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions