Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,611
Community Members
 
Community Events
176
Community Groups

Why is the default S3_KEY expanding to 'None' when using aws-elasticbeanstalk-deploy pipe?

Currently, I'm not specifying an S3_KEY when using the aws-elasticbeanstalk-deploy:1.0.1 pipe to deploy a .NET Core application bundle as a zip file.

When the pipe pushed the artifact to S3, the default value for the S3_KEY is set to ${APPLICATION_NAME}/${VERSION_LABEL}. The pipe runs as expected and deploys an artifact, but the actual artifact is uploaded with the key ${APPLICATION_NAME}/None.zip.

It seems as though the ${VERSION_LABEL} is not expanding as part of the upload function in the pipe source code, specifically line 129 in pipe/pipe.py where it calls  `self.get_variable('S3_KEY')`. I could not locate the implementation of `get_variable()`, but it appears to be returning 'None' here, which is then used to construct the 'source_bundle_key' on line 140.

Here is log output from the pipe running in debug mode showing the failed expansion 'Artifact uploaded successfully to s3://sample-s3-bucket-name/SampleAppName/None'.

 

1 answer

0 votes

Hi @Caleb Scholze

Thank you for your feedback!

We are investigating this behaviour and notify you.

 

Best regards,
Oleksandr Kyrdan

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events