-
Notifications
You must be signed in to change notification settings - Fork 157
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
Cannot read property 'Key' of undefined #27
Comments
I'm having the same issue right now. In my case, I'm using a |
@JavierMonton i just saw this. You're correct this module doesn't allow for region. I may have time create a PR this weekend. |
Hi @drpym, thanks for you comment! I think the error could be related to permissions too, in my case I found out that I had permissions for |
Hi, |
The PR is open, but you can use the Aws cli as it is preinstalled in actions. Make sure to pass AWS_REGION.
…On Sun, Jun 6, 2021 at 2:48 PM, hananmalka ***@***.***> wrote:
Hi,
Any news about this issue?
I'm having the same error and couldn't find for a solution
—
You are receiving this because you were mentioned.
Reply to this email directly, [view it on GitHub](#27 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AIZHETGO3JUY7GFRA3644ULTRPUMVANCNFSM4ZU6ZASA).
|
I had the same error. How I fixed? - Created a bucket specific policy and attached to a user and this error vanished but the new one came forward. |
For anyone else that ends up here, I believe this library requires public read access to be set. https://docs.aws.amazon.com/AmazonS3/latest/userguide/WebsiteAccessPermissionsReqd.html |
Yeah definitely don't need the public access-- For my GH hosted runners I usually use
But when dealing with my self hosted runners I usually have to do something different if I don't have access to the AWS CLI on the container running it. |
I have the following:
And get the following error:
It is not 100% clear why, wonder if it's not related to this code?
I believe the data might not be available when there is an error, so it might be due to an ACL permission (cf #21)
The text was updated successfully, but these errors were encountered: