v2.4.0

Fix cluster resizes @stroobl (#103)

what

Remove ignore changes for EBS volume size, it breaks resizes.

why

Impossible to (Terraform) resize a cluster with the current code and impossible to apply Terraform after a resize in the console, even after an import of the cluster.

I know there is ongoing work in #101 that might also include a fix for this, but it looks like it will take more time to get that done. This is a basic fix.

references

AWS provider issue: hashicorp/terraform-provider-aws#26031
Cloudposse module issue: #99

v2.3.1

🤖 Automatic Updates

Update Terraform cloudposse/security-group/aws to v2.2.0 (main) @renovate (#88)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/security-group/aws (source)	module	minor	2.1.0 -> 2.2.0

---

Release Notes

cloudposse/terraform-aws-security-group (cloudposse/security-group/aws)

v2.2.0

Compare Source

`.editorconfig` Typo @​milldr (#​50)

what

fixed intent typo

why

should be spelled "indent"

references

https://cloudposse.slack.com/archives/C01EY65H1PA/p1685638634845009

Sync github @​max-lobur (#​47)

Rebuild github dir from the template

---

v2.3.0

Fix `client_authentication` block. Update module versions @aknysh (#92)

what

• Fix client_authentication block
• Update module versions

why

• The client_authentication block was wrong for a few reasons:

  • unauthenticated was only set if any of client_tls_auth_enabled, client_sasl_scram_enabled or client_sasl_iam_enabled was set, which is wrong
  • Having sasl block as dynamic caused MSK to recreate the cluster if any of the authentication method changed (see #91)

• Keep up to date

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/msk_cluster.html#client_authentication

related

• Closes #91

v2.2.0

Fix and update variables and inputs @aknysh (#90)

what

• Fix and update variables and inputs
• Bump Go to 1.20 in terratest

why

• Remove unused (deprecated) variables
• Use all the variables that are declared
• Add missing outputs
• Fix output types and descriptions
• Fix the tflint errors:

WARNING: "tflint FILE/DIR" is deprecated and will error in a future version. Use --chdir or --filter instead.
  reviewdog: input data has violations
  security-group-variables.tf:146:1: warning: variable "allow_all_egress" is declared but not used ()
  security-group-variables.tf:202:1: warning: variable "inline_rules_enabled" is declared but not used ()
  security-group-variables.tf:212:1: warning: variable "revoke_security_group_rules_on_delete" is declared but not used ()
  security-group-variables.tf:[66](https://github.com/cloudposse/terraform-aws-msk-apache-kafka-cluster/actions/runs/5006279988/jobs/8971794698#step:6:74):1: warning: variable "allowed_ipv6_cidr_blocks" is declared but not used ()
  security-group-variables.tf:75:1: warning: variable "allowed_ipv6_prefix_list_ids" is declared but not used ()
  variables-deprecated.tf:1:1: warning: variable "security_groups" is declared but not used ()

Facilitate error-free MSK upgrades @gkramer-gloat (#86)

what

This change adds support for MSK upgrades.

why

Necessary to support MSK upgrades, rather than destroying and recreating the cluster (which was previously the case).

references

Sync github @max-lobur (#89)

Rebuild github dir from the template

v2.1.0

• No changes

v2.0.0

Update modules and tests. Refactor @aknysh (#85)

what

• Update all module versions
• Update tests
• Fix variables and outputs names

why

• Use the latest versions of all TF modules
• Update the terratest to use the latest patterns
• Keep up to date

related

• Closes #69

v1.4.0

Custom Route53 DNS hostname for MSK brokers @rooty0 (#80)

what

• Feature: customize hostname for MSK brokers

why

• The company where I work requires me to follow hostname standards. So we'd like to have control over DNS hostnames.

v1.3.1

🚀 Enhancements

Update Terraform cloudposse/route53-cluster-hostname/aws to v0.12.3 (master) @renovate (#83)

This PR contains the following updates:

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

---

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

v0.12.3

Compare Source

Add zone inputs, update tests, add usage @​nitrocode (#​42)

what

• Add zone inputs, update tests, add usage

why

• Verify zone name exists
• Dynamically retrieve zone name based on data source inputs

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/route53_zone
• Closes https://github.com/cloudposse/terraform-aws-route53-cluster-hostname/issues/41

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

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

---

🤖 Automatic Updates

Update Terraform cloudposse/route53-cluster-hostname/aws to v0.12.3 (master) @renovate (#83)

This PR contains the following updates:

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

---

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

v0.12.3

Compare Source

Add zone inputs, update tests, add usage @​nitrocode (#​42)

what

• Add zone inputs, update tests, add usage

why

• Verify zone name exists
• Dynamically retrieve zone name based on data source inputs

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/route53_zone
• Closes https://github.com/cloudposse/terraform-aws-route53-cluster-hostname/issues/41

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

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

---

v1.3.0

Make scram secret assocation optional @dougbw (#78)

what

• Make the aws_msk_scram_secret_association resource optional when sasl/scram authentication is enabled through a new variable client_sasl_scram_secret_association_enabled
• The default behaviour is the same as before

why

• The aws_msk_scram_secret_association resource is not very flexible and in certain use cases the preference is to manage the secret associations out of band from the cluster creation
• In our case we need to enable sasl/scram at the point of creating the cluster of the cluster, but need to manage sasl/scram users in another tf root
• Having aws_msk_scram_secret_association resources in separate roots creates conflicts where they will constantly overwrite each others changes

references

• See hashicorp/terraform-provider-aws#16791

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

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

v1.2.0

Update splat msk cluster ebs volume size @arcaven (#81)

what

• update splat operators
• update aws resource syntax in msk cluster for ebs_volume_size and related aws provider versioning

why

• post-terraform 0.12.0 splat format
• reduce tflint, terraform validate noise
• ebs_volume_size was deprecated from aws_msk_cluster addressing #75

references

• https://github.com/terraform-linters/tflint-ruleset-terraform/blob/v0.2.2/docs/rules/terraform_deprecated_index.md
• https://registry.terraform.io/providers/hashicorp/aws/4.15.0/docs/resources/msk_cluster#ebs_volume_size