-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Validate DC name does not contain a period #169
Comments
What should happen if it doesn't match that character class? Just drop the bad characters? Should it warn you first or fail completely? |
Yeah fail the validation, agent will refuse to start. |
Why was this a problem? The change is undocumented, and it just broke my Consul cluster: we were using DCs like |
Corollary: this issue is referenced in the changelog, but the impact is not. |
@blalor It should have broken the DNS parser to have a DC like that. Were you using the DNS interface at all? We must have mistakenly failed to put it in the change log. |
No, we weren’t using the DNS interface, yet. I see where that would cause problems, but I’d like to have seen the DC treated as an opaque string by the resolver. This also implies that dots in node names will also cause problems, correct? |
I think a dot in a node name is fine. I can look into changing the resolver to remove this limitation. |
Only write service-defaults if protocol set
DC names should match [a-zA-Z0-9-_]+
The text was updated successfully, but these errors were encountered: