v1.2.0

• No changes

v1.1.1

🚀 Enhancements

Update main.tf @amitvashisttech (#60)

In this example [ log_uri = format("s3://%s", module.s3_log_storage.bucket_id) ], which cause EMR cluster rebuild in terraform apply.

After adding a missing back slash in the log_uri definition solves the problem.

what

• Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?)
• Use bullet points to be concise and to the point.

why

• Provide the justifications for the changes (e.g. business case).
• Describe why these changes were made (e.g. why do these commits fix the problem?)
• Use bullet points to be concise and to the point.

references

• Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
• Use closes #123, if this PR closes a GitHub issue #123

v1.1.0

Adding support for SSH access via SSM agent to EMR instances @danjbh (#58)

what

• Adding boolean flag to control attachment of SSM IAM policy to EMR cluster EC2 instance profile
• README update

why

• The IAM policy provides required permission to the SSM agent, which facilitates remote SSM shell connections via the AWS console and cli.

references

• #46

v1.0.0

Update all modules, examples and tests to the latest versions and patterns @aknysh (#57)

what

• Update all modules, examples and tests to the latest versions and patterns
• Update README

why

• Keep up to date

git.io->cloudposse.tools update @dylanbannon (#52)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

• DEV-143

v0.25.0

Clarify descriptions to indicate secgroup id is required @erpel (#50)

what

• Update the description of multiple variables that called for security group names but required ids instead.

why

• To make the generated documentation more correct and helpful.

v0.24.0

Add support for auto termination policy, resolves #53 @szymonm (#55)

what

Adds support for defining auto termination policy as described in https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/emr_cluster#auto_termination_policy

why

Auto termination lets the user schedule termination of the cluster if it is idle for a predefined time.
See more in #53

references

Closes #53

v0.23.0

Add missing tags to the aws_iam_instance_profile resource. @pecastro (#54)

what

• Adding missing tags parameter to the aws_iam_instance_profile resource.

why

• Prevents linting tools from failing
• Tags the resource appropriately in line with the tagging strategy.

references

*https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_instance_profile#tags

v0.22.3

🤖 Automatic Updates

chore(deps): update terraform cloudposse/route53-cluster-hostname/aws to v0.12.2 @renovate (#47)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/route53-cluster-hostname/aws (source)	module	patch	0.12.0 -> 0.12.2

---

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

v0.12.2

Compare Source

🚀 Enhancements

Bump AWS provider 3.0 @​nitrocode (#​36)

##### what * Bump AWS provider 3.0 ##### why * Downstream modules can take advantage of the more recent aws provider ##### references N/A

v0.12.1

Compare Source

🚀 Enhancements

Chore: run `make github/init` @​korenyoni (#​37)

#### what * Run `make github/init`. #### why * Updates GHA-workflow-related files to their latest distribution. * The old `context.tf` distribution is incompatible with the `tenant` label. #### references * https://github.com/cloudposse/terraform-null-label/releases/tag/0.25.0

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

v0.22.2

🚀 Enhancements

Upgrade aws provider to 3.0 @nitrocode (#45)

what

• Upgrade aws provider to 3.0

why

• Fixes a bug in the provider. See related issues.

references

• Closes #26 and possibly #15

v0.22.1

🤖 Automatic Updates

chore(deps): update terraform cloudposse/label/null to v0.25.0 @renovate (#48)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/label/null (source)	module	minor	0.24.1 -> 0.25.0

---

Release Notes

cloudposse/terraform-null-label

v0.25.0

Compare Source

Add "tenant", "labels_as_tags", and "descriptors" @​Nuru (#​132)

##### what - Add additional label and `id` component: `tenant` - New input `labels_as_tags` controls which labels are exported as tags - New input `descriptor_formats` generates new output `descriptors` - Update README, remove link to obsolete `terraform-terraform-label` ##### why - Support users that host resources on behalf of and/or dedicated to single customers - Supersedes and closes #​131, giving people control over which tags the module generates - Simple mechanism for creating multiple identifiers from the same inputs, reducing the need to create multiple instances of `null-label` - Document `tenant`, `labels_as_tags`, `descriptor_formats`, add additional clarification, stop promoting obsolete module

Fix: Update README Snippets @​korenyoni (#​130)

##### what * Update README snippets to reflect use of Terraform Registry. ##### why * Including snippets that reflect use of the Terraform Registry make it easier for users to quickly instantiate a null_label module. * README is out of date and does not include snippets that reflect use of the Terraform Registry. ##### references * N/A

Bridgecrew compliance @​Nuru (#​125)

##### what - Resolve Bridgecrew compliance complaint about example Autoscaling Group (BC_AWS_GENERAL_31) - Fix typo in README - Include Terraform lock file in `.gitignore` ##### why - Get clean Bridgecrew badge - Correct confusing error - Ensure lock files are not checked into GitHub ##### note The PR can and should be merged into `master` to update README and Bridgecrew without triggering a new release/version. These changes have no effect on the actual module in use and a release will create unnecessary ripple effects. However, merging to `master` will update the README and badges, so is worthwhile, and the changes will move forward into the next release.

Properly output descriptors of chained modules @​Nuru (#​133)

##### what - Properly output descriptors of chained modules ##### why - Bug fix; implement intended behavior

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.