-
-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
null reader endpoint address #236
Comments
I see 2 coalesce statements. From your description only the reader endpoint is affected when in cluster mode. terraform-aws-elasticache-redis/main.tf Line 113 in 23723dd
terraform-aws-elasticache-redis/main.tf Line 119 in 23723dd
The docs say to use the configuration endpoint
https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Endpoints.html Since we use the aws_elasticache_replication_group resource we can add this output to the coalesce
What do you think? |
It also fails when
|
as cluster_endpoint doesn't have reader endpoint, that's why when you try to read |
Describe the Bug
Since version 1.3.0, terraform plan fails with an existing cluster (running in cluster mode) as all the reader endpoint options are null.
Expected Behavior
Terraform plan with no changes to an existing cluster should just successfully plan and show no changes.
Steps to Reproduce
Create a cluster using version 1.2.0 of this module. Update to version 1.3.0. Run terraform plan.
Screenshots
Error observed during terraform plan
Environment
TERRAFORM_VERSION: 1.5.6
OS: ubuntu (github actions)
terraform-aws-elasticache-redis version: 1.3.0
Additional Context
Elasticache doesn't give you a reader endpoint when using redis in cluster mode, only a configuration endpoint, so
is always going to be
coalesce(null, null, null)
if you're using cluster mode, and is always going to throw this error.The text was updated successfully, but these errors were encountered: