0.7.0: Updates to ChatOps - Automated commit (#17)

## What
* Adds chatops commands
  - '/test all'
  - '/test bats'
  - '/test readme'
  - '/test terratest'
* Drops codefresh
* Drops slash-command-dispatch
* Removes codefresh badge
* Rebuilds README

## Why
* Change over from codefresh to GH Actions
* Facilitate testing of PRs from forks

0.6.0 Added kerberos_attributes configuration

what

• Added kerberos_attributes configuration

why

• To enhance security of cluster

0.5.0 Add variable to control S3 endpoint creation

what

• Add the variable create_vpc_endpoint_s3 to control VPC S3 Endpoint creation

why

• Users may already have their own S3 Endpoint in the selected VPC. If they do, this module fails because there can only be one.

0.4.0 Prevent EMR cluster recreation when javax.jdo.option.ConnectionPassword is used in configuration_json

what

• Bootstrap action added that executes /bin/echo and as an argument md5 hash of configuration_json - dummy action
• configuration_json added to lifecycle/ignore_changes

why

• When configuration_json uses javax.jdo.option.ConnectionPassword then terraform will force recreate cluster with every apply. Reason for that is that AWS API for describe_cluster returns configuration with string '********instead of real password forjavax.jdo.option.ConnectionPassword. terraform` want to replace that "masked" password with actual password.

references

• #13
• hashicorp/terraform-provider-aws#12683
• hashicorp/terraform-provider-aws#7733

0.3.0 Add `application-autoscaling.amazonaws.com` as Trusted entity

what

• Add application-autoscaling.amazonaws.com as Trusted entity

why

• When using autoscaling, the autoscaling policy is failing to attach with the error:

Failed to provision the AutoScaling policy: Unable to assume IAM role: arn:aws:iam::*********:role/emr-stage-dataorc-emr-ec2-autoscaling

this is due to absence of application-autoscaling.amazonaws.com as Trusted entity

0.2.1 Add `configurations_json`. Fix `bootstrap_action`

what

• Add configurations_json
• Fix bootstrap_action

why

• Closes #3
• Closes #4

0.2.0 Fix security groups. Set `visible_to_all_users` to `true`

what

• Update egress for EMR managed security groups
• Set visible_to_all_users to true

why

• EMR will create and maintain rules for all managed security groups for master, slave and service access (when in private subnet). EMR will add all the required ingress and egress rules to the groups

• When you specify managed security groups for a cluster, you must use the same type of security group, default or custom, for all managed security groups. For example, you can't specify a custom security group for the master instance, and then not specify a custom security group for core and task instances.

• If visible_to_all_users is set to false, the cluster, after it's created, is not visible in the AWS console and even to terraform user that created it

references

• https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-sg-specify.html
• https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-man-sec-groups.html
• https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-clusters-in-a-vpc.html

0.1.0 Initial implementation

what

• Initial implementation of terraform-aws-emr-cluster module

why

• Provision an Elastic MapReduce (EMR) cluster on AWS