bugfix: rest path resolution #3032
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stobrien89
force-pushed
the
rest-path-resolution-fix
branch
2 times, most recently
from
6a37f60 to
d3fcf88
Compare
yenfryherrerafeliz
approved these changes
Nov 21, 2024
stobrien89
force-pushed
the
rest-path-resolution-fix
branch
from
d3fcf88 to
0326488
Compare
stobrien89
force-pushed
the
rest-path-resolution-fix
branch
from
0326488 to
9896706
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue #, if available:
#3030
Description of changes:
Fixes issue with non-s3 services (only Location V2 services currently) whose endpoint ruleset models a URI with a path.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.