-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Allow AWS Secrets Backends use AWS Connection capabilities #25628
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow AWS Secrets Backends use AWS Connection capabilities #25628
Conversation
626797f to
461f5ab
Compare
o-nikolas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These code modules are a little obtuse (not your fault) so it's difficult to review with high confidence, but I've had a look and left some comments
461f5ab to
3d42954
Compare
83d3ca2 to
b5060c0
Compare
I hope in near future we could also drop all deprecated configs, which makes it easier to maintain and expand. BTW, finally fix/change suggestion and pass tests |
vincbeck
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The secrets tests are interacting with providers so changes in providers secrets implementation might break those tests. Moving them to "always" folder prevents them from accepting a PR that breaks other PRs. Related: apache#25751 apache#25628
In additional added new Extra Connection parameters
profile_name- this only one parameter which could be assigned tosession_kwargswithout any side effects in current provider, so I thought there is no reason usesession_kwargs.verify- this parameter could specified at that moment only in hook (right now), but not in connection.Update documentation and split Extra Connection Config by sections.
closes: #25326 (updated, initially mention wrong issue)