Service pages not rendering in UI for services with special characters in name

[freddygv]

In the 1.8.0-beta1 release there is a bug in a UI query to the /connect/intentions endpoint that leads to some service pages not being rendered.

Services with non-alphanumeric characters in their name need to be wrapped in quotes when using Consul's endpoint filtering.

Not wrapping names with special characters in quotes leads to a 500 response from Consul. This 500 response leads to the service page not being rendered. Instead of the service page the UI will instead show a page that says The backend responded with an error and Error 500.

The workaround for this while testing with 1.8.0-beta1 is to only register services with alphanumeric characters or underscores _ in the name.

The fix has already been merged in #7888 and will be available in 1.8.0-beta2. Creating this issue for visibility.

[freddygv]

Fixed by #7888