You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to set up my S3 cache so that CI runs on pull requests can read from the cache, but for security reasons they shouldn't be able to write to it. I tried this by
making AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY GitHub Secrets. GitHub Actions make sure that they're only available when built in a branch of the repository, not on PRs.
making the S3 bucket publicly readable
Now, unfortunately, action-s3-cache doesn't seem to be able to read public S3 buckets. If I omit the AWS_SECRET_ACCESS_KEY and AWS_ACCESS_KEY_ID variables when calling it, it fails with an error
2021/04/25 23:45:09 NoCredentialProviders: no valid providers in chain. Deprecated.
For verbose messaging see aws.Config.CredentialsChainVerboseErrors
What's the best way to make this work?
The text was updated successfully, but these errors were encountered:
I'd like to set up my S3 cache so that CI runs on pull requests can read from the cache, but for security reasons they shouldn't be able to write to it. I tried this by
AWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
GitHub Secrets. GitHub Actions make sure that they're only available when built in a branch of the repository, not on PRs.Now, unfortunately, action-s3-cache doesn't seem to be able to read public S3 buckets. If I omit the
AWS_SECRET_ACCESS_KEY
andAWS_ACCESS_KEY_ID
variables when calling it, it fails with an errorWhat's the best way to make this work?
The text was updated successfully, but these errors were encountered: