Skip to content

Releases: skyscrapers/terraform-codedeploy

Fix base64 output path

11 Mar 08:45
Compare
Choose a tag to compare
3.0.2

Fix base64 output path

Fixing a syntax error with app module

03 Jul 12:37
689d83b
Compare
Choose a tag to compare
3.0.1

Fixing a syntax error introduced in #16

Refactor deployment groups sub modules

24 Apr 13:36
e7bc7b9
Compare
Choose a tag to compare

All deployment groups submodules have been refactored into a single module, some variables names have been changed. Make sure to check the latest README before updating from previous versions

Add dyncmaic load_balancer_info block

01 Apr 14:16
15bf195
Compare
Choose a tag to compare
2.0.2

Add dyncmaic load_balancer_info block (#18)

Fix path.module workaround

09 Aug 08:40
1a9f34c
Compare
Choose a tag to compare

The workaround was applied to fix a bug that has been resolved by Terraform 0.12

2.0.0 Update code to terraform 0.12

16 Jul 11:49
2c8d528
Compare
Choose a tag to compare

This release bumps the modules used by monitoring in order to make the module compatible with tf 0.12

1.6.0

12 Apr 12:59
d3846c3
Compare
Choose a tag to compare

This release adds the option to specify a blue/green codedeploy deployment with default tested parameters for a basic setup.

More information can be found here:
https://aws.amazon.com/blogs/devops/performing-bluegreen-deployments-with-aws-codedeploy-and-auto-scaling-groups/

Add Slack Notifications and better formatting

22 Nov 15:51
bb7b3ec
Compare
Choose a tag to compare
  • Slack mentions are now possible for Codedeploy failures, including channel and here with e.g. <!channel>.
  • Improved the formatting of the Codedeploy Slack messages, including colour coding
  • A verbose option to reduce the amount of Codedeploy messages seen in Slack, if the Codedeploy triggers have not already been trimmed.

Fix static name for iam policy

28 Sep 11:47
571e647
Compare
Choose a tag to compare
Merge pull request #12 from SevereOverfl0w/master

Add a prefix to the codedeploy policy for the S3 bucket

Slack Notify no longer needs an S3 bucket

03 May 07:44
7c00574
Compare
Choose a tag to compare

Replaces full path with a relative path which means an S3 bucket is not needed for the Lamda code for the slack notification.