fix(#360): recreates AWS SSO client when the region changes #361
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
This commit fixes the case when the region for AWS SSO changes and the client isn't aware, leading to the "Session token not found or invalid" error. It adds a check to see if the clients' region is different to the integration one and so recreate the client. Signed-off-by: Mauricio Wyler <[email protected]>
|
Merged and closed, thanks you all! |
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.
This commit fixes the case when the region for AWS SSO changes and the client isn't aware, leading to the "Session token not found or invalid" error.
It adds a check to see if the clients' region is different to the integration one and so recreate the client.
Signed-off-by: Mauricio Wyler [email protected]
Changelog
If SSO region changes the AWS SSO client is recreated
Bugfixes
#360