Skip to content

fix: add EndpointRequired config resolver to replace CustomEndpoint #1628

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

Merged
merged 1 commit into from
Jun 23, 2025

Conversation

kuhe
Copy link
Contributor

@kuhe kuhe commented Jun 23, 2025

in #1589, I added a "default endpoint ruleset" for all clients. This aligned all codegen for consistency and removed edge cases not covered by AWS SDK testing (AWS SDKs all have endpoint rulesets).

In EP2.0, the endpoint input is not required. This makes client calls to await client.config.endpoint() fail a typecheck, because prior to #1589, a resolver layer called "CustomEndpoint" marked the endpoint input as required when not in the endpoints-ruleset code generation mode.

This PR adds backwards compatibility with the CustomEndpoint resolver layer without bringing it back. Here, I add a EndpointRequired config resolver layer when using the default endpoint ruleset.

@kuhe kuhe requested a review from a team as a code owner June 23, 2025 14:21
@kuhe kuhe changed the title fix/custom endpoint fix: add EndpointRequired config resolver to replace CustomEndpoint Jun 23, 2025
@kuhe kuhe force-pushed the fix/custom-endpoint branch from 7818f72 to a9ab1ab Compare June 23, 2025 14:25
@kuhe kuhe merged commit 22a286e into smithy-lang:main Jun 23, 2025
11 checks passed
@kuhe kuhe deleted the fix/custom-endpoint branch June 23, 2025 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants