Removing unused sts v2 dependency - #93
Open
vaisharma wants to merge 1 commit into
Open
Conversation
guizmaii
approved these changes
Jan 31, 2023
Closed
Contributor
|
I think this change is not safe. If I remember correctly, the v2 sts and sso dependencies are needed at runtime if an aws profile is used that depends on a role or single signon credential. The v2 sdk which is used to load the profile based credentials tries lazy loading them from the classpath at runtime. So, we need to still have the v2 sts and sso dependencies. |
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
3 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.
Description of changes:
The sts V2 dependency is not needed for the package. So removing it.