0.6.1 Move hardcoded scaling settings into variables

what

• Move hardcoded scaling settings into variables
• Fix wrong variable description

why

• To be able to choose what kind of auto scaling triggers to use

0.6.0 Use `terraform-terraform-label` instead of `terraform-null-label`

what

• Use terraform-terraform-label instead of terraform-null-label

why

The terraform-null-label grew a bit complex and is throwing errors when used:

* module.sc-api-env-active.module.elastic_beanstalk_environment.module.label.data.null_data_source.tags_as_list_of_maps: data.null_data_source.tags_as_list_of_maps: 
value of 'count' cannot be computed

0.5.0 Add `force_destroy` option for S3 bucket

what

Add force_destroy option for S3 bucket

why

After running destroy the S3 bucket for load balancer logs is not destroyed

0.4.9

what

• Add aws:elasticbeanstalk:container:nodejs for NodeVersion settings

why

• To be able to deploy different NodeJS versions

0.4.8

what

Add the possibility to use existing security groups when creating load balancer, and stop the creation of the default security group.

why

The default behavior when creating a load balancer is to create a security group which allow 0.0.0.0 to access to it. Sometimes we need to allow only a specific CIDR.

There are two variables :

• loadbalancer_security_groups : list of security groups to attach
• loadbalancer_managed_security_group : A single SG. If you don't fill this variable, it will continue to create a default security group.

Example : Use a custom SG which allow only my network :

  loadbalancer_security_groups = ["${module.sg.this_security_group_id}"]
  loadbalancer_managed_security_group = "${module.sg.this_security_group_id}"

If you don't fill theses two variables, you have the classical workflow.

references

• https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-general-elasticbeanstalkmanagedactionsplatformupdate
• https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-general-elbv2
• https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-general-elbloadbalancer

0.4.7

what

• Bump terraform-null-label version
• Make zone_id optional

why

• New terraform-null-label version fixes the issue with empty tag values (which breaks Elastic Beanstalk environment)
• Don't create a DNS record if zone_id is empty. Not all applications require a friendly DNS name for EB environment

0.4.6

what

• Add usage example

why

• Make it easier for people to start using the module
• Used by Terraform registry

Regenerate README.md

what

• Regenerate README.md

why

• Previous version of build-harness has some typos

0.4.4: Ignore tag changes (#40)

* Ignore tag changes 

followup of #37

* format code to please linter

0.4.3

what

• Remove invalid S3 actions

why

There are a few S3 actions which are invalid and therefore are not being applied to the role.