v0.42.1

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

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 (#163)

This PR contains the following updates:

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

---

v0.42.0

Add tags to aws_elasticache_subnet_group @jddcarreira (#150)

what

• Adds tags to the AWS resource aws_elasticache_subnet_group

why

• good practices

v0.41.6

🚀 Enhancements

Re-adding tag propagation for cloudwatch alarms @brucehajdu (#147)

what

In #7, the tag propagation was removed for CloudWatch metric alarms because the tags property did not exist at that time. This PR adds them back.

why

• Terraform has had the capability to manage tags for aws_cloudwatch_metric_alarm resources for a while now, so I think we should add it back, as I think it makes sense for tags to propagate to all possible resources managed by the module.
• This also helps me to comply with my organization's tagging policies without the hassle of manual intervention.

references

• PR where the tags were removed: #7
• Terraform docs showing tags as a valid option for metric alarms: aws_cloudwatch_metric_alarm
• Closes #148

v0.41.5

🤖 Automatic Updates

chore(deps): update terraform cloudposse/security-group/aws to v0.4.3 @renovate (#146)

This PR contains the following updates:

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

---

Release Notes

cloudposse/terraform-aws-security-group

v0.4.3

Compare Source

Update recommended inputs and outputs @​Nuru (#​26)

#### what - Update recommended inputs and outputs #### why - Changes based on experience implementing several modules

#### 🚀 Enhancements

Rename the exported `security_group_inputs.tf` file to `security-group-inputs.tf` @​aknysh (#​30)

#### what * Rename the exported `security_group_inputs.tf` file to `security-group-inputs.tf` * Update GitHub workflows and LICENSE #### why * Our naming convention is to use `kebab-case` for all files. Having a file in `snake_case` (after adding it to a repo) together with all the other files in `kebab-case` in the same repo does not look correct * Keep up to date

---

v0.41.4

🚀 Enhancements

fix: make parameter group description configurable @syphernl (#143)

what

• This allows to set the description of a Parameter Group to prevent recreation.

why

• Before v0.41.3 no description was set, so this defaulted to Managed by Terraform.
  As the description cannot be changed without recreating the Parameter Group this caused issues with existing resources.

references

• Refs #142, #144

v0.41.3

🚀 Enhancements

Small fixes - convert param values to string, set auto failover to true if cluster enabled @nitrocode (#141)

what

• Small fixes
• Convert param values to string
• Set auto failover to true if cluster enabled
• Add descriptions to subnet and param groups

why

• Param values will fail if they are not strings

  InvalidParameterValue: invalid parameter value, allowed values are:yes,no
  

• Auto failover needs to be set to true if cluster mode is enabled or it will fail with an error

  InvalidParameterValue: Redis with cluster mode enabled cannot be created with auto failover turned off.
  

references

• Thanks to @simoferr98 this closes #140

v0.41.2

🐛 Bug Fixes

Fix #137 bad output when cluster_mode_enabled=true @Nuru (#139)

what

• Fix #137 bad output when cluster_mode_enabled=true
• Add migration documentation

why

• join("", [null]) results in a Terraform error
• Should have been included in v0.40.0

references

• Closes #137
• Supersedes and closes #138

v0.41.1

🐛 Bug Fixes

Bugfixes @Nuru (#136)

what

• Always pass string for zone_id for route53-cluster-hostname module
• Never pass null for security_group_id for aws_elasticache_replication_group

why

• Errors otherwise

references

• Closes #134
• Supersedes and closes #135

v0.41.0

Upgrade to new securty-group standards @Nuru (#133)

what

• Upgrade to new Cloud Posse security group standards
• Enable proper operation when DNS zone is created at the same time as the cluster
• 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 additional outputs for the Redis Replication Group

why

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

references

• Closes #82
• Closes #86
• Closes #104
• Closes #113
• Closes #121
• Closes #127
• Supersedes and closes #130
• Supersedes and closes #132

v0.40.3

🤖 Automatic Updates

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

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/route53-cluster-hostname/aws (source)	module	patch	0.12.1 -> 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

---

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.