Releases: cloudposse/terraform-aws-emr-cluster
Releases · cloudposse/terraform-aws-emr-cluster
v0.16.0
update emr module to use existing security groups @tirumerla (#33)
what
- Allow EMR module to use existing managed and additional security groups created outside this module.
why
- Make EMR module flexible for users to use their own security groups if they already have one or create new security groups if they don't have existing security group or doesn't want to use one.
v0.15.0
Include Steps option in aws_emr_cluster @hannahkamundson (#30)
what
You should be able to add steps to this module.
why
It was initially requested to allow debugging, but it should allow a user to add any steps that they can in the main AWS EMR Terraform
references
closes #7
v0.14.0
v0.13.0
fix: add ingress rule from managed master to service @svrakitin (#22)
what
- add ingress rule on TCP 9443 from managed master to service security group
why
- emr-5.30.* requires this rule to be present
references
v0.12.0
v0.11.0
Add support for step_concurrency_level @calvin-barker (#25)
what
- This adds support for the
step_concurrency_levelvariable when deploying EMR clusters (with release >= 5.28.0)
why
- I need to send multiple steps that run in parallel to my EMR cluster, and the current CloudPosse template doesn't support that
references
v0.10.0
fix: unquote references in ignore_changes @svrakitin (#21)
what
- remove terraform 0.11 warnings, i.e.:
on .terraform/modules/emr_cluster/main.tf line 467, in resource "aws_emr_cluster" "default":
467: ignore_changes = ["kerberos_attributes", "step", "configurations_json"]
In this context, references are expected literally rather than in quotes.
Terraform 0.11 and earlier required quotes, but quoted references are now
deprecated and will be removed in a future version of Terraform. Remove the
quotes surrounding this reference to silence this warning.
why
- avoid these warnings in logs
v0.9.0
0.8.1: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#18)
## 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.