fix(*): fix sts regional endpoint support - #62
Merged
Conversation
Tieske
previously approved these changes
Jul 17, 2023
Member
Author
|
I added a changelog for this PR, @Tieske can you approve this again? Thanks! |
Tieske
approved these changes
Jul 18, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
The sts regional endpoint inject happens after
build_requestwhich means that when you called STS service withAWS_STS_REGIONAL_ENDPOINT=regionalthe first time, it will not work. This PR fixes that behaviour and also adds tests to check regional endpoint injection works as expected.After the PR I can verify that the regional endpoint will be in the request
Fix FTI-5211