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

Skip rules based endpoints for most services #3520

Merged
merged 9 commits into from Oct 27, 2022
Merged

Conversation

dagnir
Copy link
Contributor

@dagnir dagnir commented Oct 26, 2022

Motivation and Context

Modifications

We are only enabling rules based endpoints for S3, S3Control, and EventBridge for now in order to roll back incorrect hostprefix handling in the Java SDK. S3, S3Control, and EventBridge are unaffected by this issue because their rules are handwritten, and in the case of S3Control which has a host prefix in the model, it is handled by the rule set.

Testing

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING document
  • Local run of mvn install succeeds
  • My code follows the code style of this project
  • My change requires a change to the Javadoc documentation
  • I have updated the Javadoc documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed
  • I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
  • My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

  • I confirm that this pull request can be released under the Apache 2 license

We are only enabling rules based endpoints for S3, S3Control, and EventBridge
for now in order to roll back incorrect hostprefix handling in the Java SDK. S3,
S3Control, and EventBridge are unaffected by this issue because their rules are
handwritten, and in the case of S3Control which has a host prefix in the model,
it is handled by the rule set.
@dagnir dagnir requested a review from a team as a code owner October 26, 2022 21:27
@dagnir dagnir enabled auto-merge (squash) October 26, 2022 21:35
@zoewangg
Copy link
Contributor

Integ tests passed

@zoewangg zoewangg enabled auto-merge (squash) October 27, 2022 18:23
@zoewangg zoewangg merged commit 0140729 into master Oct 27, 2022
@sonarcloud
Copy link

sonarcloud bot commented Oct 27, 2022

SonarCloud Quality Gate failed.    Quality Gate failed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 1 Code Smell

58.8% 58.8% Coverage
3.4% 3.4% Duplication

debora-ito pushed a commit to debora-ito/aws-sdk-java-v2 that referenced this pull request Oct 28, 2022
* Skip rules based endpoints for most services

We are only enabling rules based endpoints for S3, S3Control, and EventBridge
for now in order to roll back incorrect hostprefix handling in the Java SDK. S3,
S3Control, and EventBridge are unaffected by this issue because their rules are
handwritten, and in the case of S3Control which has a host prefix in the model,
it is handled by the rule set.


Co-authored-by: John Viegas <joviegas@amazon.com>
Co-authored-by: Zoe Wang <33073555+zoewangg@users.noreply.github.com>
dagnir added a commit that referenced this pull request Nov 29, 2022
This changes fixes the previously incorrect handling of `hostPrefix` in
services, causing requests for some services to have the wrong URL. This change
also undoes the suppression of rules-based endpoint generation for all services
apart from EventBridge, S3, and S3 Control, which was implemented in #3520
because of the previously mentioned `hostPrefix` issue.
dagnir added a commit that referenced this pull request Dec 1, 2022
This changes fixes the previously incorrect handling of `hostPrefix` in
services, causing requests for some services to have the wrong URL. This change
also undoes the suppression of rules-based endpoint generation for all services
apart from EventBridge, S3, and S3 Control, which was implemented in #3520
because of the previously mentioned `hostPrefix` issue.
dagnir added a commit that referenced this pull request Dec 1, 2022
This changes fixes the previously incorrect handling of `hostPrefix` in
services, causing requests for some services to have the wrong URL. This change
also undoes the suppression of rules-based endpoint generation for all services
apart from EventBridge, S3, and S3 Control, which was implemented in #3520
because of the previously mentioned `hostPrefix` issue.
dagnir added a commit that referenced this pull request Dec 2, 2022
* Support HostPrefix in E2.0, enable E2.0 for all services

This changes fixes the previously incorrect handling of `hostPrefix` in
services, causing requests for some services to have the wrong URL. This change
also undoes the suppression of rules-based endpoint generation for all services
apart from EventBridge, S3, and S3 Control, which was implemented in #3520
because of the previously mentioned `hostPrefix` issue.

* Review comments

* Set tokenProvider() for Bearer auth services
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.

None yet

4 participants