-
Notifications
You must be signed in to change notification settings - Fork 193
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
Add aws irsa auth #1021
base: master
Are you sure you want to change the base?
Add aws irsa auth #1021
Conversation
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
@@ -102,6 +103,7 @@ def __init__( | |||
self, | |||
url, | |||
encryption=None, | |||
aws_irsa=False, |
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.
please relocate this new argument at the end of the argument list to preserve the original signature @smcaine
@smcaine thanks for your contribution. I've put a suggestion in the code during my review of the pr. The code seems correct but your patch has broken the Unit Tests for Barman, because of this we cannot merge the PR as it is. Could you fix the failing tests? FYI we are working on some contribution guidelines for PRs and what I'm asking will be part of this new documentation section. Thanks. |
181e3bb
to
f6c55a5
Compare
Hi Stuart, as mentioned before, your PR is failing for tox tests. Can you check these and push a fix that makes them pass? https://github.com/EnterpriseDB/barman/actions/runs/11720727101/job/32805402247?pr=1021 There are also flack errors that need addressing: https://github.com/EnterpriseDB/barman/actions/runs/11720727101/job/32805400982?pr=1021 |
Adding this flag to use the service account iam role. Using aws access keys is bad practice and typically prohibited in most production environments.
This relates to issue i raised #949