Use regular expressions to validate tailscale hostname #2714 #2719
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #2714
@Hooverdan96, @phillxnet: ready for review.
Following up on @Hooverdan96's suggestion to leverage regular expressions to better validate the hostname key in the Tailscale service config.
The current mechanism uses a hard-coded list of characters to exclude them from a custom tailscale hostname if present. This is rather ugly and does not scale to all the characters (such as unicode) that need to be excluded.
Switch to using regular expressions to exclude only characters from the hostname that do not belong to that regular expression.
All tests still pass...
... and I was able to configure and turn ON the Tailscale service with a custom hostname being taken in effect (as seen on the Tailscale machines dashboard).