Describe the bug:
When creating an auto-follow pattern for cross-cluster replication, the part that defines the prefix and suffix has is no validation on special characters or uppercase characters what would lead to invalid index names in Elasticsearch, but it has a warning about the special characters. Nothing in this warning speaks about uppercase characters, which are also invalid in Elasticsearch.
Steps to reproduce:
Navigate to Stack Management / Cross-Cluster Replication / Auto-follow patterns
Create auto-follow pattern
Add uppercase characters in the prefix and suffix. No warnings about this type anywhere in the screen. See screenshot below
Create an index matching the pattern. Auto-follow will fail and GET _ccr/stats will tell you Invalid index name [...], must be lowercase. See screenshot below.
Expected behavior:
It would be great to have at least a warning about uppercase characters, if not a fully fledged validation, to prevent similar issues.
Kibana version: 7.14.0
Describe the bug: When creating an auto-follow pattern for cross-cluster replication, the part that defines the prefix and suffix has is no validation on special characters or uppercase characters what would lead to invalid index names in Elasticsearch, but it has a warning about the special characters. Nothing in this warning speaks about uppercase characters, which are also invalid in Elasticsearch.
Steps to reproduce:
GET _ccr/stats
will tell youInvalid index name [...], must be lowercase
. See screenshot below.Expected behavior: It would be great to have at least a warning about uppercase characters, if not a fully fledged validation, to prevent similar issues.
Screenshots (if relevant):