`sam deploy` does not use specified S3 bucket in samconfig.toml

Description:

Attempting to use a previously configured S3 bucket for deployments by specifying the s3_bucket parameter in the samconfig.toml does not work.

Steps to reproduce:

1. Create an S3 bucket with the same bucket policy as the SAM CLI’s dynamically created default source bucket.
2. Update your 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)
3. Run sam build --guided.

Observed result:

Note the Deployment s3 bucket in the output provided:

Deploying with following values
===============================
Stack name                         : process-lambda
Region                                 : us-east-1
Confirm changeset            : True
Deployment image repository  : 
                                       {
                                           "ProcessFunction": "834609584094.dkr.ecr.us-east-1.amazonaws.com/dev-scrb-process"
                                       }
Deployment s3 bucket         : aws-sam-cli-managed-default-samclisourcebucket-1w6spftg6a31d <<<<
Capabilities                           : ["CAPABILITY_IAM"]
Parameter overrides            : {}
Signing Profiles                    : {}

Expected result:

The Deployment s3 bucket should use the supplied s3_bucket value configured in the samconfig.toml file (either arn:aws:s3:::bucket-name or bucket-name.

Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

1. OS:MacOS
2. SAM CLI, version 1.17.0
3. AWS region: us-east-1

[Jacco]

Current SAM version is 1.34.0. Have you tried upgrading?

[warrior8792]

I believe this still exists in SAM CLI v1.66.0