Deploy with Codedeploy task about aws-toolkit-azure-devops

[stevejroberts]

There's not currently a way inside the CodeDeploy task itself.

We could extend the task to include all the encryption options from the S3 Upload task, but that would add quite a bit of complexity to the task configuration (although I guess we could put them into a section and collapse it by default). There are a bunch of other tasks (eg Beanstalk deployment) that also do S3 uploads on behalf of the build - if we start to copy the encryption settings in there too, things really start to bloat.

Since the S3 Upload task already handles the encryption part of things, how about if we extended the CodeDeploy task (and others where relevant) with an option to indicate the bundle already exists in S3 due to a prior upload? Would that work for you?

[andyjcooper]

Hi Steve,

Thanks for the speedy reply.

Yes that would be perfect.

Many thanks
Andy

[stevejroberts]

Working on it :-)

[andyjcooper]

Awesome, many thanks Steve.

[stevejroberts]

I've just released v1.0.17 to the marketplace with the update. The CodeDeploy task now contains an option allowing you to specify the deployment bundle should come from a folder or file in the build workspace (the default option) or from a previously uploaded archive in S3.

Hope this does what you need; if so I'll extend the support to the Elastic Beanstalk task too.

[andyjcooper]

Hi Steve,

I've tested this out and is all working! Many thanks for your help in getting this updated so quickly.

Cheers
Andy

[stevejroberts]

Good to know, I'll get this extended to the Beanstalk task too. Resolving :-)