-
Notifications
You must be signed in to change notification settings - Fork 196
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
fix(ecr): only set credentials if username & password is specified, refactor to use aws-sdk v3 #128
Conversation
Can you prune your cache just in case? |
9a70db5
to
ce8a232
Compare
Tried nuking my docker cache and also Disabled autocrlf and I was able to stag it and force push I'm running on WSL |
Interestingly enough its just one part of the file that had line changes e307f4e |
Marked as draft again as it failed manual test on our runner. Will have to pause this for now! |
Signed-off-by: Markus Maga <[email protected]>
0b36861
to
5885569
Compare
const credentials = | ||
username && password | ||
? { | ||
accessKeyId: username, | ||
secretAccessKey: password | ||
} | ||
: undefined; |
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.
You beat me to it, this should fix #129
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.
Yes! 😄 just saw the test branch :)
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.
Should allow it to fallback to the default credential chain that the aws-sdk uses
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 thanks!
Related to #126