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

Add a new smithy-modeled rules based endpoint resolution. #2214

Merged
merged 58 commits into from
Jul 31, 2023
Merged

Conversation

isaiahvita
Copy link
Contributor

This PR adds a significant feature to support smithy-modeled rules-based endpoint resolution which will supercede and deprecate existing endpoint resolution.

Copy link
Contributor

@aajtodd aajtodd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix and ship

.github/workflows/codegen.yml Outdated Show resolved Hide resolved
service/accessanalyzer/api_client.go Outdated Show resolved Hide resolved
isaiahvita and others added 27 commits July 31, 2023 08:44
Adds model preprocessing for S3 and S3 control due to EP 2.0 resolution handling certain bindings and host prefixes.

- `S3ControlHostPrefixAccountIdFilterIntegration`
- `S3HttpPathBucketFilterIntegration`
- `S3HostPrefixRequestRouteFilterIntegration`
… HTTP client, instead of talking to an actual loopback server which was causing issues with dns resolution in ep2 (#2174)
Previously, properties were not being stored correctly, so the path for EP 2.0 Auth Scheme resolution was not being hit.

After the fix from aws/smithy-go#434 was merged, issues happened in the new code path.
* Check S3 signer customization insensitively
* Check EventBridge signer customization insensitively
@isaiahvita isaiahvita merged commit 26bf48f into main Jul 31, 2023
12 of 15 checks passed
@lucix-aws lucix-aws deleted the feat-ep20 branch May 6, 2024 14:48
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.

3 participants