Resolve and validate AWS Connection parameters in wrapper #25256
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.
Separate class which help resolve and validate AWS connection parameters.
Currently, might for historical reason, connections properties validate/read/resolve/construct in
BaseSessionFactory
andAwsGenericHook
in different methods.This changes would help to make changes/deprecate in AWS Connection settings easier than now - need to make changes in one place, rather tried to found in multiple places.
Also it should make easier tests Connections configuration relates.
WDYT? @o-nikolas @ferruzzi
Note:
BaseSessionFactory
still use connection configs for SAML and Web Federation, I have to plan remove this in the further PRs