Make s3 (mostly) work with preSRA #4496
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.












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,:s3passes locally with both useSraAuth = false (in this PR) and true (tested locally).Screenshots (if appropriate)
Types of changes
Checklist
mvn installsucceedsscripts/new-changescript and following the instructions. Commit the new file created by the script in.changes/next-releasewith your changes.License