AWS S3 Deploy Pipe Issues

Samuel Bloch September 6, 2023

When trying to use the S3 pipe, it doesn't work if there are spaces in the local path

 

- pipe: atlassian/aws-s3-deploy:1.1.0
variables:
AWS_ACCESS_KEY_ID: $AWS_KEY # Optional if already defined in the context.
AWS_SECRET_ACCESS_KEY: $AWS_SECRET # Optional if already defined in the context.
AWS_DEFAULT_REGION: "us-east-1"
S3_BUCKET: "foo-bucket/bazz/"
LOCAL_PATH: "$BITBUCKET_CLONE_DIR/foo bar/folder"
This will fail.

1 answer

1 vote
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 6, 2023

Hi Samuel,

Are you able to use the latest version of the pipe and see if you experience the same behaviour (1.3.0)?

Also, try creating a repository variable with the entire path and pass this through using this variable in the pipe parameters - does this make any difference?

The last thing I would try is to escape the path using ' single quotes instead of " double quotes.

Cheers!

- Ben (Bitbucket Cloud Support)

Igor Stoyanov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 8, 2023

@Samuel Bloch hi. Also some useful link about escaping.

Regards, Igor

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events