Skip to content

Releases: cloudposse/terraform-aws-elastic-beanstalk-environment

0.28.0

18 Aug 08:31
427b9cc
Compare
Choose a tag to compare
LB resources only for LoadBalanced env type (#130)

0.27.0: Terraform 0.12 setting fix (#132)

18 Aug 08:17
ff101e6
Compare
Choose a tag to compare
* further fixes for #114

* spot instance variables and dynamic variables where not covered
* sorting for securitygroups was not enough

those two issues resulted in still having terraform plan showing changes
even if no changes were present.

* change SpotMaxPrice setting to be dynamic

* formatting changes

ran terraform fmt to reformat changes

* Revert "formatting changes"

This reverts commit 1b2f723410e37f8ea518a9083364414efc51e5c8.

* redo formatting changes due to wrong email

Co-authored-by: Jan Nonnen <[email protected]>
Co-authored-by: Jan Nonnen <[email protected]>

0.26.1

18 Aug 07:47
b088b4c
Compare
Choose a tag to compare
[AUTOMATED] Update terraform-null-label versions to support Terraform…

0.26.0: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#129)

18 Aug 07:47
a9e0f10
Compare
Choose a tag to compare
## What

1. Update Version Pinning for Terraform to support 0.13

## Why

1. This is a relatively minor update that the CloudPosse module already likely supports.
1. This allows module consumers to not individually update our Terraform module to support Terraform 0.13.

0.25.0: Configuration option for disabling Cross Zone Load Balancing (for classic LB)

05 Aug 16:55
7f7491a
Compare
Choose a tag to compare

what

  • The Cross Zone Load Balancing option for the classic LB was hardcoded to true. This allows a user disable the cross zone if needed.

why

  • Reduce costs for regional data transfer
  • Minimize latency

0.24.0: Add deployment configuration options (#120)

03 Jul 00:09
dfc707e
Compare
Choose a tag to compare

what

  • adds configuration options to the deployment as described in the section aws:elasticbeanstalk:command of the general options documentation
  • current defaults are kept and for options that haven't been set so far the AWS default is used

why

  • we want to configure the deployments in more detail - especially the current configuration of Fixed deployment with 1 instance at a time can be slow

references

0.23.0

02 Jul 23:13
0db185a
Compare
Choose a tag to compare
Adding new ChatOps (#121)

0.22.0 feat: add support for ami_id

26 May 09:24
0cdd527
Compare
Choose a tag to compare

what

  • Added support for specifying ami_id

why

  • ami_id is a key configurable option in EB environments

references

0.21.0 Settings changes fix

26 May 07:39
b809467
Compare
Choose a tag to compare

what

  • Fix of #43 for terraform 0.12.x for now and separated classic & application ELB settings

why

  • As #43 shows, terraform 0.12.x shows settings changes during terraform planwhen no changes were done.
  • furthermore, if you are using an application load balancer the classic ELB settings are always shown as changes. I used the AWS documentation of "deprecated" classic ELB values if you are using an ALB to decide which settings go into which of the two lists.

references

  • closes #43 for terraform 0.12.x

0.20.0 Add support for spot instances

26 May 06:44
a9bda0e
Compare
Choose a tag to compare

what

  • Allow usage of spot instances in beanstalk environments

why

  • We want to use spot instances in some of our beanstalk environments and this was missing in the module

references

  • closes #100