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

provider/aws: Add expanded name as output to route53_record #1847

Merged
merged 1 commit into from
May 8, 2015

Conversation

radeksimko
Copy link
Member

This is a follow-up PR to #1126

With this change, the following:

${aws_route53_record.log.name}.${aws_route53_zone.primary.name}

can be shortened to this:

${aws_route53_record.log.fqdn}

and more importantly if the zone is part of another module, I don't have to pass in the domain as a string into the module where I'm creating a record.

I'm still not entirely sure about the name - fqdn, it could also be expanded_name, what do you think @catsby ?

@radeksimko
Copy link
Member Author

@justincampbell What do you think of the suggested name here?

@phinze
Copy link
Contributor

phinze commented May 8, 2015

I, for one, like FQDN (if the value as constructed is indeed an FQDN)

@justincampbell
Copy link
Contributor

fqdn sounds ok. dnsimple_record exports hostname.

The Route53 interface uses value as the host, and name as the fully-qualified name. However, it also uses name as the domain name in other places.

I would usually defer to whichever terminology the Route53 API/docs/UI uses, but I think fqdn is very clear about what it is.

@radeksimko
Copy link
Member Author

Cool, I will just add this to docs then and 🚢

@radeksimko radeksimko force-pushed the add-fqdn-to-route53 branch from 75b2041 to ce8351d Compare May 8, 2015 19:19
radeksimko added a commit that referenced this pull request May 8, 2015
provider/aws: Add expanded name as output to route53_record
@radeksimko radeksimko merged commit 6409c5b into hashicorp:master May 8, 2015
@radeksimko radeksimko deleted the add-fqdn-to-route53 branch May 8, 2015 19:23
@ghost
Copy link

ghost commented May 2, 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 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.

@ghost ghost locked and limited conversation to collaborators May 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants