Closed xirkus closed 3 years ago
Current SAM version is 1.34.0. Have you tried upgrading?
@Jacco SAM Version is 1.34 but the CLI version is 1.17. They are not versioned separately.
Transferring to the correct repo as this relates to SAM CLI not SAM the spec.
I'm closing this issue as I could not reproduce it with the latest version of the SAM CLI. Please comment if you are still experiencing this.
I'm still experiencing this with SAM CLI 1.26.0 on Amazon Linux 2 OS. Although my issue is with sam deploy --guided
instead.
The issue is still happening on SAM CLI v1.37.0
Still facing this issue with SAM CLI v1.55.0
I believe this still exists in SAM CLI v1.66.0
same issue on SAM CLI, version 1.73.0 for "sam deploy --guided" also --s3-bucket didnt work
Works fine apparently without the --guided
flag
Description:
Attempting to use a previously configured S3 bucket for deployments by specifying the
s3_bucket
parameter in thesamconfig.toml
does not work.Steps to reproduce:
samconfig.toml
to include this new bucket's ARN:s3_bucket = "arn:aws:s3:::bucket-name"
(although I tried with the bucket name as well)sam build --guided
.Observed result:
Note the
Deployment s3 bucket
in the output provided:Expected result:
The
Deployment s3 bucket
should use the supplieds3_bucket
value configured in thesamconfig.toml
file (eitherarn:aws:s3:::bucket-name
orbucket-name
.Additional environment details (Ex: Windows, Mac, Amazon Linux etc)