Hi This fixes problems when authed only using Serverless' SERVERLESS_ACCESS_KEY env variable, AWS credentials stored in Serverless dashboard. (not with locally stored aws credentials or aws-cli)
S3 sync was working this way only with bucketName and not with bucketNameKey, due to these differences in credentials. This MR only reuses the method originally from client() method again in resolveStackOutput. It doesn't change any logic (including the comments).
Hi This fixes problems when authed only using Serverless'
SERVERLESS_ACCESS_KEY
env variable, AWS credentials stored in Serverless dashboard. (not with locally stored aws credentials or aws-cli)S3 sync was working this way only with
bucketName
and not withbucketNameKey
, due to these differences in credentials. This MR only reuses the method originally fromclient()
method again inresolveStackOutput
. It doesn't change any logic (including the comments).I believe this is also related/possible fix to https://github.com/k1LoW/serverless-s3-sync/issues/66