v0.19.4

Dual stack support @ngoyal16 (#88)

## what

Memcache cluster can be run in 3 network modes - ipv4, ipv6 or dual_stack.
Underlying module already supports this parameter

why

It can be mandatory to enable it to be able to connect from dual_stack or ipv6 only runtimes

references

🤖 Automatic Updates

Migrate new test account @osterman (#87)

## what - Update `.github/settings.yml` - Update `.github/chatops.yml` files

why

• Re-apply .github/settings.yml from org level to get terratest environment
• Migrate to new test account

References

• DEV-388 Automate clean up of test account in new organization
• DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
• DEV-386 Update terratest to use new testing account with GitHub OIDC

Update .github/settings.yml @osterman (#86)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update .github/settings.yml @osterman (#85)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update .github/settings.yml @osterman (#84)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update release workflow to allow pull-requests: write @osterman (#83)

## what - Update workflow (`.github/workflows/release.yaml`) to have permission to comment on PR

why

• So we can support commenting on PRs with a link to the release

Update GitHub Workflows to use shared workflows from '.github' repo @osterman (#81)

## what - Update workflows (`.github/workflows`) to use shared workflows from `.github` repo

why

• Reduce nested levels of reusable workflows

v0.19.3

fix: elasticache_subnet_group creation @flightlesstux (#79)

what

• If we pass elasticache_subnet_group_name, the aws_elasticache_subnet_group.default[0] won't be created anymore

why

• Who needs a new elasticache_subnet_group even we already created before and just want to pass a name

references

• Check issue #78

🤖 Automatic Updates

Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#80)

what

• Update workflows (.github/workflows) to add issue: write permission needed by ReviewDog tflint action

why

• The ReviewDog action will comment with line-level suggestions based on linting failures

Update GitHub workflows @osterman (#77)

what

• Update workflows (.github/workflows/settings.yaml)

why

• Support new readme generation workflow.
• Generate banners

v0.19.2

Set correct required version of AWS provider @nicolajv (#76)

what

Sets the required AWS provider version to v5.16, the minimal requirement for use of the module.

why

With the introduction of the transit_encryption_enabled variable this module now requires AWS provider v5.16, as that is the version to introduce that attribute to the aws_elasticache_cluster resource.

references

• AWS Provider v5.16 changelog

🤖 Automatic Updates

Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#75)

what

• Install latest GitHub Action Workflows

why

• Use shared workflows from cldouposse/.github repository
• Simplify management of workflows from centralized hub of configuration

Add GitHub Settings @osterman (#73)

what

• Install a repository config (.github/settings.yaml)

why

• Programmatically manage GitHub repo settings

Add GitHub Settings @osterman (#72)

what

• Install a .github/settings.yaml

why

• Programmatically manage GitHub repo settings

Update README.md and docs @cloudpossebot (#70)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

Update Scaffolding @osterman (#71)

what

• Reran make readme to rebuild README.md from README.yaml
• Migrate to square badges
• Add scaffolding for repo settings and Mergify

why

• Upstream template changed in the .github repo
• Work better with repository rulesets
• Modernize look & feel

chore(deps): update terraform cloudposse/vpc/aws to v2.2.0 @renovate (#68)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/vpc/aws (source)	module	minor	2.1.1 -> 2.2.0

---

Release Notes

cloudposse/terraform-aws-vpc (cloudposse/vpc/aws)

v2.2.0

Compare Source

---

chore(deps): update terraform cloudposse/vpc/aws to v2.1.1 @renovate (#65)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/vpc/aws (source)	module	patch	2.1.0 -> 2.1.1

---

Release Notes

cloudposse/terraform-aws-vpc (cloudposse/vpc/aws)

v2.1.1

Compare Source

Add support for network address usage metrics @​lanzrein (#​124)

what

This PR adds support for Network Address Usage Metrics on the VPC.
AWS documentation : https://docs.aws.amazon.com/vpc/latest/userguide/network-address-usage.html
Terraform documentation : https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpc#enable_network_address_usage_metrics

why

Network Address Usage metrics can help monitor the growth of a VPC and would be useful for any user.
Enable this after creating a VPC does not trigger recreation of the VPC.

references

closes #​115

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

Rebuild github dir from the template

🤖 Automatic Updates

Update README.md and docs @​cloudpossebot (#​125)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

---

v0.19.1

🚀 Enhancements

fix: sg arn output breaks when providing security groups IDs @pcn (#67)

what

Currently a join() is run over what is assumed to be all of the created security groups created by the module.aws_security_group. This join fails when there are no security groups being created. What's more, my reading is that only one security group will ever be created, so only one security group ID should ever need to be extracted, so this is probably a leftover from older logic.

why

When using create_security_group = false and associated_security_groups = [<something>] , the module fails with

│ Invalid value for "lists" parameter: element 0 is null; cannot concatenate
│ null values.

This breaks a documented supported configuration (that we happen to use and be blocked by).

references

This is just putting the fix from https://github.com/dmitrijn/terraform-aws-elasticache-memcached per the request in #56 (comment) to get this fix into main.

🐛 Bug Fixes

fix: sg arn output breaks when providing security groups IDs @pcn (#67)

what

Currently a join() is run over what is assumed to be all of the created security groups created by the module.aws_security_group. This join fails when there are no security groups being created. What's more, my reading is that only one security group will ever be created, so only one security group ID should ever need to be extracted, so this is probably a leftover from older logic.

why

When using create_security_group = false and associated_security_groups = [<something>] , the module fails with

│ Invalid value for "lists" parameter: element 0 is null; cannot concatenate
│ null values.

This breaks a documented supported configuration (that we happen to use and be blocked by).

references

This is just putting the fix from https://github.com/dmitrijn/terraform-aws-elasticache-memcached per the request in #56 (comment) to get this fix into main.

v0.19.0

Add Encryption-in-Transit support @LuisDeHaro (#66)

what

Add Encryption-in-Transit support to the module.

why

For compliance reasons, some companies require transit level encryption across cloud resources. Cache-stores are no exception.

references

ElastiCache Memcached Encryption-in-Transit documentation: https://docs.aws.amazon.com/AmazonElastiCache/latest/mem-ug/in-transit-encryption.html

v0.18.0

Add support for aws provider v5 and newer TF @MaxymVlasov (#62)

Plus fixes from

make init
make github/init
make readme

Sync github @max-lobur (#57)

Rebuild github dir from the template

v0.17.0

• No changes

v0.16.0

Groundwork new workflows @max-lobur (#54)

Fix lint/format before workflows rollout

v0.15.1

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

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

chore(deps): update terraform cloudposse/security-group/aws to v1 @renovate (#48)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/security-group/aws (source)	module	major	0.4.3 -> 1.0.1

---

v0.15.0

🚀 Enhancements

Security group updates @danjbh (#43)

NOTE: The work in this PR mirrors the security group updates performed in cloudposse/terraform-aws-elasticache-redis#133, since these modules are very similar.

what

• Upgrade to new Cloud Posse security group standards
• Enable create_before_destroy on security groups by default
• Update AWS provider version constraint to properly require a version that has all the features the module uses
• Add security group ARN and name to outputs.tf

why

• Further standardize all Cloud Posse modules
• Supply bug fixes and features requested via "issues".