-
Notifications
You must be signed in to change notification settings - Fork 8
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
Rename poorly-named DNS variables #61
Conversation
The naming of the variables that describe the DNS zone to which we're adding records (dns_tld_external), the name of the domain part of the FQDN (cluster_vars.dns_zone_external), and the name of the domain part of the cloud-internal FQDN (dns_zone_internal) is very poor, and leads to misunderstandings. dns_tld_external --> cluster_vars.dns_nameserver_zone dns_zone_internal --> cluster_vars.dns_cloud_internal_domain dns_zone_external --> cluster_vars.dns_fqdn_domain
Alternative suggestions welcome... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Not entirely sure I like the way the internal and external diverge naming wise, and they are not technically fqdns? (There is no hostname). Could I suggest the below:
I think the |
Agree with your comment on diverging, however
True! In addition to my above suggestion, perhaps
This way there is no divergence across vars and the naming convention for dns vars will always be |
Of course, missed that - yep suggestion looks good to me, and I think |
If I can live without the
|
This LGTM - I'm also ok with |
The naming of the variables that describe the DNS zone to which we're adding records (
dns_tld_external
), the name of the domain part of the FQDN (cluster_vars.dns_zone_external
), and the name of the domain part of the cloud-internal FQDN (cluster_vars.dns_zone_internal
) is very poor, and leads to misunderstandings.