Invalid Node Names Behave Inconsistently
Posted: March 15th, 2023, 9:58 pm
Service names prevent a lot of invalid characters, but one thing they do allow are invalid first characters.
For example, numbers and hyphens are not valid as the first character of a node name.
When using invalid names for services like "2CSN2" or "-CSN-b", the invalid characters seem like they are escaped upon execution to be "_x0032_CSN2" and "_x002D_CSN-b" respectively.
When using the assistant for referencing those services however, it provides the unescaped version which then causes other errors.
When using invalid names for services parameters like "1param", no escaping happens at all.
Invalid service parameter names cause parsing errors that can be seen in the logs.
The log image also shows how the invalid service names were escaped.
For example, numbers and hyphens are not valid as the first character of a node name.
When using invalid names for services like "2CSN2" or "-CSN-b", the invalid characters seem like they are escaped upon execution to be "_x0032_CSN2" and "_x002D_CSN-b" respectively.
When using the assistant for referencing those services however, it provides the unescaped version which then causes other errors.
When using invalid names for services parameters like "1param", no escaping happens at all.
Invalid service parameter names cause parsing errors that can be seen in the logs.
The log image also shows how the invalid service names were escaped.