Skip to content

Conversation

@gosar
Copy link
Contributor

@gosar gosar commented Sep 28, 2023

Motivation and Context

This is follow up from #4491, where I forced s3 to useSraAuth=true path since tests were failing with useSraAuth=false. Fixing it here, mostly**.

Note this PR builds on #4495 as the base branch.

This PR brings some of deleted codegen code related to endpoint rules back from #4311. That PR deleted the EndpointAuthSchemeInterceptor and put related logic in EndpointResolverInterceptor. Not fully undoing that here, but logic related to old Signer is brought back, now into
EndpointResolverInterceptor, when useSraAuth=false.

**Now endpoints related tests in s3 pass, except for 3 tests related to whether forward slash is added to endpoint. There's an existing TODO related to that, so temporarily disabling it.

Modifications

Testing

./mvnw clean install -pl :codegen,:s3 passes locally with both useSraAuth = false (in this PR) and true (tested locally).

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

@gosar gosar force-pushed the gosar/sra-ia-s3control-preSRA branch from db74c34 to 6228139 Compare September 28, 2023 09:00
This brings some of deleted codegen code related to endpoint rules
back from #4311. That PR
deleted the EndpointAuthSchemeInterceptor and put related logic in
EndpointResolverInterceptor. Not fully undoing that here, but logic
related to old Signer is brought back, now into
EndpointResolverInterceptor, when useSraAuth=false.

Now endpoints related tests in s3 pass, except for 3 tests related to
whether forward slash is added to endpoint. There's an existing TODO
related to that, so temporarily disabling it.
@gosar gosar force-pushed the gosar/sra-ia-s3-preSRA branch from 5f2bd5b to 88064eb Compare September 28, 2023 09:04
@gosar gosar marked this pull request as ready for review September 28, 2023 09:09
@gosar gosar requested a review from a team as a code owner September 28, 2023 09:09
@gosar gosar changed the base branch from gosar/sra-ia-s3control-preSRA to feature/master/sra-identity-auth September 28, 2023 16:51
@gosar gosar merged commit b44d0a6 into feature/master/sra-identity-auth Sep 28, 2023
@gosar gosar deleted the gosar/sra-ia-s3-preSRA branch September 28, 2023 16:52
@sonarqubecloud
Copy link

SonarCloud Quality Gate failed.    Quality Gate failed

Bug C 4 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot E 2 Security Hotspots
Code Smell A 450 Code Smells

84.2% 84.2% Coverage
4.0% 4.0% Duplication

idea Catch issues before they fail your Quality Gate with our IDE extension sonarlint SonarLint

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