atlassian/aws-elasticbeanstalk-deploy:1.0.1 S3_KEY is "None"

[Ian Anderson]

With the changeover to Python for the aws-elasticbeanstalk-deploy pipe, the "S3_KEY" is set to 

'{os.getenv("APPLICATION_NAME")}/{os.getenv("VERSION_LABEL")}' by default. However, "VERSION_LABEL" is not a required field, and as such is set independently to a logical value if not provided in the configuration. However, when setting "S3_KEY" this is not taken into account. The current default will make it so all versions are uploaded to S3 with "APPLICATION_NAME"/"None. this means that the zip files for all versions collide with the name "None" in S3,. 

Either the default for S3_KEY should be set to use the same logic as the VERSION_LABEL, VERSION_LABEL should become required, or another reasonable default should be set that gives a valid, different name for the uploaded zip file for each deploy.

[Halyna Berezovska · Accepted solution]

@Ian Anderson could you please share the part of pipeline, so we can see the precise pipeline configuration and it will help us to reproduce it?

Regards, Galyna

[Ian Anderson]

 - step: &deploy 
     name: Deploy 
     deployment: test 
     script:
       - pipe: atlassian/aws-elasticbeanstalk-deploy:1.0.1
         variables: 
           APPLICATION_NAME: $APPLICATION_NAME 
           ENVIRONMENT_NAME: $APPLICATION_ENVIRONMENT 
           ZIP_FILE: "composer_build.zip" 
           S3_BUCKET: $S3_BUCKET

[Halyna Berezovska]

@Ian Anderson please, try our newest pipe

 atlassian/aws-elasticbeanstalk-deploy:1.0.2

Looking forward to seeing your feedback

Regards, Galyna

[Ian Anderson]

@Halyna Berezovska - It is working well from my end. The initial build I tried has been completely successful. 

thank you!

[Oleksandr Kyrdan]

Hi @Ian Anderson

Thank you for your feedback!

We'll fix this behaviour and notify you.

Best regards,
Oleksandr Kyrdan