diff --git a/CHANGELOG.md b/CHANGELOG.md index 2e3997336..7060761e4 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,59 @@ # CHANGELOG +## 1.522.0 + + + +## 🚀 Enhancements + +
+ feat(elasticache-redis): add engine input for valkey support @nitrocode (#1170) +## what + + +- add engine input for valkey support + +## why + + +- Valkey is far cheaper than redis + +
Notes + +- Design options + 1. Add a new key to `local.cluster_attributes` and add a variable to the component, default it to `redis`, and pass as an argument to the module as-is + - We could shy away from the pattern to using `engine = var.engine` in the `local`. + 1. Allow `var.redis_clusters` to supply `engine` with a default for `redis` and pass to module as-is + 1. Same as option 2 but allow `local.cluster_attributes` to overwrite it + - This might be best of both worlds however no other argument does this so it would be breaking the pattern +- Went with option 2 so the argument isn't a new requirement for everyone and it doesn't break consistency + +
+ +## references + + +- https://github.com/cloudposse/terraform-aws-elasticache-redis/releases/tag/v1.7.0 +- https://aws.amazon.com/blogs/opensource/why-aws-supports-valkey/ +- https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/elasticache_replication_group#engine +- https://github.com/hashicorp/terraform-provider-aws/issues/39641 +- https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.73.0 +- https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/Clusters.Create.html +- https://www.lastweekinaws.com/blog/aws-valkey-play-when-a-fork-becomes-a-price-cut/ +
+ + + ## 1.517.1