Skip to content
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

The documentation for AWS ElastiCache replication group is wrong/incomplete #375

Closed
hashibot opened this issue Jun 13, 2017 · 4 comments · Fixed by #1542
Closed

The documentation for AWS ElastiCache replication group is wrong/incomplete #375

hashibot opened this issue Jun 13, 2017 · 4 comments · Fixed by #1542
Labels
bug Addresses a defect in current functionality. documentation Introduces or discusses updates to documentation.

Comments

@hashibot
Copy link

This issue was originally opened by @FransUrbo as hashicorp/terraform#10128. It was migrated here as part of the provider split. The original body of the issue is below.


Trying to create a AWS ElastiCache replication group and then a Route53 entry for that gives me an error.

The documentation say:

configuration_endpoint_address - (Redis only) The address of the replication group configuration endpoint when cluster mode is enabled.

but this don't seem to be the case.

Terraform Version

0.7.8

Affected Resource(s)

  • aws_elasticache_replication_group

Terraform Configuration Files

resource "aws_elasticache_replication_group" "autoscaling_event_update_route53" {
  replication_group_id          = "asgevnt-route53"
  replication_group_description = "Autoscaling events updating Route53"

  engine_version                = "3.2.4"
  node_type                     = "cache.m3.medium"
# => The number of replicas per node group must be within 0 and 5.
  number_cache_clusters         = "${length(data.aws_availability_zones.available.names)}"
  port                          = 6379

  subnet_group_name             = "${aws_elasticache_subnet_group.main.name}"
  security_group_ids            = [
    "${aws_security_group.main-all.id}"
  ]
  parameter_group_name          = "default.redis3.2"

  automatic_failover_enabled    = "true"
  availability_zones            = ["${data.aws_availability_zones.available.names}"]
  apply_immediately             = "true"
  maintenance_window            = "sun:01:00-sun:02:00"

  tags {
    Name                        = "autoscaling_event_update_route53"
    environment                 = "core"
    service                     = "main"
  }
}

resource "aws_route53_record" "elasticache" {
 zone_id               = "${aws_route53_zone.main.zone_id}"
 name                  = "elasticache.${var.dns_zone}"
 type                  = "A"
 ttl                   = "300"
 records               = ["${aws_elasticache_replication_group.autoscaling_event_update_route53.configuration_endpoint_address}"]
}

Gives * Resource 'aws_elasticache_replication_group.autoscaling_event_update_route53' does not have attribute 'configuration_endpoint_address' for variable 'aws_elasticache_replication_group.autoscaling_event_update_route53.configuration_endpoint_address'

Looking at the ElastiCache Dashboard, it instead uses Primary Endpoint with Configuration Endpoint: -.

@hashibot hashibot added bug Addresses a defect in current functionality. documentation Introduces or discusses updates to documentation. labels Jun 13, 2017
@Ninir
Copy link
Contributor

Ninir commented Aug 28, 2017

Hi @FransUrbo

Are you still having this issue in TF 0.10.2?

Thanks!

@Ninir Ninir added the waiting-response Maintainers are waiting on response from community or contributor. label Aug 28, 2017
@FransUrbo
Copy link

Not sure, I solved it by using primary_endpoint_address instead in the aws_route53_record resource.

I've never tried going back to using configuration_endpoint_address (and now I'm live so I'm reluctant to try - using primary_endpoint_address works).

However, if I look at the state file, there is no configuration_endpoint_address value anywhere.

@Ninir
Copy link
Contributor

Ninir commented Aug 30, 2017

As far as I checked, configuration_endpoint_address is set when Redis is not clusterized, whereas primary_endpoint_address is used for Redis in a cluster mode.
So for your use-case, you were right!

Closing since you seem to have resolve it :)

Checking the documentation separately!

@Ninir Ninir closed this as completed Aug 30, 2017
@Ninir Ninir removed the waiting-response Maintainers are waiting on response from community or contributor. label Aug 30, 2017
@ghost
Copy link

ghost commented Apr 11, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. documentation Introduces or discusses updates to documentation.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants