v0.38.0

Support ebs_throughput to enable using of gp3 @dm3ch (#150)

what

• Support ebs volume thoughtput option

why

• Cause documentation says that this option is required for gp3 volume type

references

• #141
• #110

v0.37.0

Added AutoTune support @dm3ch (#149)

what

• Add support for AutoTune

why

• Provide support of AutoTune feature

references

• closes #121

v0.36.0

Update go.sum terratest version `0.31.4` @goruha (#151)

what

• Update go.sum terratest version

why

• Fix tests

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

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.35.1

🚀 Enhancements

fix when awareness is disabled, always changing @sanarena (#123)

what

When we disable zone awareness, Terraform want to put in availability_zone_count on every single run,
so resource is always marked as changed.
This pull request fix this issue.

why

Avoid unnecessary AWS calls and changes.

v0.35.0

feat: add validation to availability_zone_count @morremeyer (#122)

what

• This ensures that availability_zone_count is only set to allowed values, see https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/elasticsearch_domain#availability_zone_count.

why

• Without this change, it’s possible to set zone_awareness_enabled to true which will automatically use 2 AZs, but set availability_zone_count to 1, which is confusing

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/elasticsearch_domain#availability_zone_count.

v0.34.1

🚀 Enhancements

set security group lifecycle @lgiuliani-mwb (#119)

what

Added a lifecycle to the security group.

why

While importing an existing resource-set to this module, if the SG had a different name, it will try to destroy the security group while attached to the cluster instances. The lifecycle optin will first create a new one, apply the change to the cluster and then destroy the unused SG.

references

AWS doesn't allow security group to be renamed, Terraform will try to destroy and re-create it, it won't catch the error but will timeout trying to destroy a security group with attached interfaces.

v0.34.0

cein/feature/add-iam-permissions-boundary-input @Cein-Markey (#120)

what

Add new iam_role_permissions_boundary variable with a default of empty string and place it in aws_iam_role.elasticsearch_user.permissions_boundary

why

This change is to allow users of the API to leverage/set permissions boundaries: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html

"A permissions boundary is an advanced feature for using a managed policy to set the maximum permissions that an identity-based policy can grant to an IAM entity"

v0.33.3

🤖 Automatic Updates

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

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, check this box.

---

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

v0.33.2

🤖 Automatic Updates

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

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.

v0.33.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#113)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.