Releases: cloudposse/terraform-aws-elastic-beanstalk-environment
Releases · cloudposse/terraform-aws-elastic-beanstalk-environment
0.19.0 Add environment var
what
Environment
variable
why
- Most cloudposse modules have
environment
variable. This one doesn't. The PR fixes it.
0.18.0 Allow additional security groups to EC2 instances
what
- Allow additional security groups to EC2 instances
why
- Allow to specify a list of existing security groups to be allowed to connect to the EC2 instances
0.17.0 Add `dns_subdomain` var to control final hostname
what
- Add
dns_subdomain
var to control final hostname
why
dns_subdomain
allows a more customized name than the default name provided so consumers can scope their subdomains by environment or other custom needs
0.16.0 Remove `Namespace` from Elastic Beanstalk environment tags
what
- Remove
Namespace
from Elastic Beanstalk environment tags
why
Namespace
should be removed as well asName
from the tags since any string that containsName
forces recreation
0.15.0 Add `env_vars` variable
what
- Add
env_vars
variable
why
- Make it easier for the clients to provide ENV vars (as a map of key/value pairs) to the applications running on Elastic Beanstalk instead of providing ENV vars in the more complicated
setting
block
0.14.0 Convert to TF 0.12. Add tests. Add Codefresh test pipeline
what
- Port module to Terraform 0.12
- Pin all providers
- Add example for testing
- Add
bats
andterratest
for the example - Add Codefresh badge to point to the test pipeline in
terraform-modules
project - Update README
why
- Module currently does not work with 0.12. Much easier syntax
- Better regression control
- Automatically test the example on every commit and pull request
- Provision resources on AWS in the test account and check the outputs for the correct values
terraform-modules
project contains pipelines for all terraform modules
0.13.0 Add `AWSElasticBeanstalkMulticontainerDocker` role for EC2 instance profile
what
- Add
AWSElasticBeanstalkMulticontainerDocker
role for EC2 instance profile
why
- 64bit Amazon Linux 2018.03 v2.11.9 running Multi-container Docker 18.06.1-ce (Generic) solution stack needs at least ecs:RegisterContainerInstance on EC2 instance to work properly
- Closes #79
0.12.0 Add Loadbalancer stickiness option
what
- Add Loadbalancer stickiness option
why
- Session stickiness option supported by the Application load balancer and classic Load balancer
0.11.1 Update the example solution stack name
0.11.0 Add variable for application port and remove hard-coded values
what
- Add variable for application port and remove hard-coded values
why
- To be able to run applications on ports other than 80