Releases: cloudposse/terraform-aws-elasticache-redis
Releases · cloudposse/terraform-aws-elasticache-redis
v0.28.0
v0.27.3
🤖 Automatic Updates
chore(deps): update terraform cloudposse/route53-cluster-hostname/aws to v0.10.0 @renovate (#101)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/route53-cluster-hostname/aws (source) | terraform | minor | 0.9.0 -> 0.10.0 |
Release Notes
cloudposse/terraform-aws-route53-cluster-hostname
v0.10.0
Terraform 0.14 upgrade @maximmi (#32)
#### what - Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard #### why - Support Terraform 0.14v0.27.2
🤖 Automatic Updates
chore(deps): update terraform cloudposse/route53-cluster-hostname/aws to v0.9.0 @renovate (#99)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/route53-cluster-hostname/aws (source) | terraform | minor | 0.8.0 -> 0.9.0 |
Release Notes
cloudposse/terraform-aws-route53-cluster-hostname
v0.9.0
Update `context.tf` and github actions @htplbc (#31)
#### what * Update to `context.tf` #### why * Keep the module up to datev0.27.1
v0.27.0
v0.26.1
Fix release badge URL @joe-niland (#91)
what
- Badge URL referenced another repo
why
- Avoid confusion!
references
- None
v0.26.0
Added Egress Outbound Variable & Updated Redis Family in Example @barissekerciler (#90)
what
- Added cidr block option to egress traffic (default is 0.0.0.0/0)
- Updated example with Redis 6.x
why
- Business case (PCI-DSS). If you want to put Redis cluster to the private subnet, it shouldn't outbounds traffic to the all. At least, for a module, it must be opitonal.
v0.25.0
Add `cloudwatch_metric_alarms_enabled` variable. Update Terratest. Update to `context.tf` @aknysh (#84)
what
- Add
cloudwatch_metric_alarms_enabled
variable - Update Terratest
- Update to
context.tf
why
- Allow disabling CloudWatch metrics alarms
- Standardization and interoperability
- Keep the module up to date
related
v0.24.0
v0.23.0
Fix cloudwatch alarm failure to create (#56) @varunpalekar (#77)
what
- Create multiple cloudwatch alarms for each node of cluster.
why
- You can't create a cloudwatch alarm on cluster, need to create on each node of cluster.
references
- closes #56