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

aws_route53_record does not display alias names correctly #8013

Closed
chris-brace opened this issue Mar 19, 2019 · 2 comments · Fixed by #10672
Closed

aws_route53_record does not display alias names correctly #8013

chris-brace opened this issue Mar 19, 2019 · 2 comments · Fixed by #10672
Labels
bug Addresses a defect in current functionality. service/route53 Issues and PRs that pertain to the route53 service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Milestone

Comments

@chris-brace
Copy link

chris-brace commented Mar 19, 2019

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v0.11.13
+ provider.aws v2.1.0
+ provider.helm v0.9.0
+ provider.kubernetes v1.5.2

Affected Resource(s)

  • aws_route53_record

Terraform Configuration Files

resource "aws_route53_record" "a_record" {
  zone_id = "${data.aws_route53_zone.brace.zone_id}"
  name    = XXXXXXX
  type    = "A"

  alias {
    name                   = "dualstack.${data.aws_elb.nginx-ingress.dns_name}"
    zone_id                = "${data.aws_elb.nginx-ingress.zone_id}"
    evaluate_target_health = false
  }
}

Plan output

  ~ aws_route53_record.a_record
      alias.2394777190.evaluate_target_health:  "false" => "false"
      alias.2394777190.name:                    "a730c7bd249cb11e9b40b0a9d4fc1bd8-419703141.us-east-2.elb.amazonaws.com" => ""
      alias.2394777190.zone_id:                 "Z3AADJGX6KTTL2" => ""
      alias.~1237102533.evaluate_target_health: "" => "false"
      alias.~1237102533.name:                   "" => "${data.aws_elb.nginx-ingress.dns_name}"
      alias.~1237102533.zone_id:                "" => "${data.aws_elb.nginx-ingress.zone_id}"

Expected Behavior

the alias name should be "dualstack." for alias.xxx.name

Actual Behavior

only the ELB hostname shows up for alias.xxx.name

Steps to Reproduce

  1. terraform apply

Important Factoids

nothing that i can tell is different. this is how i set up the aws_elb: it scrapes it out of k8s by looking for the service installed by nginx-ingress.

data "kubernetes_service" "nginx_ingress" {
  metadata {
    name      = "${var.nginx_ingress["helm_name"]}-controller"
    namespace = "nginx-ingress"
  }

  depends_on = ["helm_release.nginx_ingress"]
}

data "aws_elb" "nginx-ingress" {
  name = "${element(split("-", element(split(".", data.kubernetes_service.nginx_ingress.load_balancer_ingress.0.hostname), 0)), 0)}"
}

References

maybe its related to this??

for more info on why dualstack. should really always be prefixed in this situation, search for dualstack on this page https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-values-alias.html

@bflad bflad added the service/route53 Issues and PRs that pertain to the route53 service. label Mar 19, 2019
@aeschright aeschright added the needs-triage Waiting for first response or review from a maintainer. label Jun 24, 2019
@aeschright aeschright added bug Addresses a defect in current functionality. and removed needs-triage Waiting for first response or review from a maintainer. labels Dec 9, 2019
@github-actions
Copy link

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Nov 30, 2021
@github-actions
Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 23, 2022
@github-actions github-actions bot added this to the v4.24.0 milestone Jul 26, 2022
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. service/route53 Issues and PRs that pertain to the route53 service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants