Howdy gang 
As part of our ongoing efforts to improve the reliability and stability of our services, we have recently added a new validation rule to the service’s artifact/manifest identifier. This rule ensures that the artifact identifier matches a specific pattern, which is defined as follows:
- The string must begin with a letter or underscore.
- The string must be between 1 and 128 characters in length.
- The string may contain letters, numbers, and underscores.
This change will help us to maintain a consistent and reliable service environment, and it will help to prevent errors and issues that can arise when artifact identifiers are not properly formatted.
If you have an existing service that contains an artifact with an identifier that does not match this pattern, you may experience an error when trying to update the service configuration. However, this will not be a problem for pipeline executions.
To fix this issue, all you need to do is update the artifact identifier to match the new pattern. This can be done by editing the service configuration and updating the identifier to match the pattern ^[a-zA-Z_][0-9a-zA-Z_]{0,127}$. Once you have done this, you should be able to save the updated configuration without any problems.
In summary, the new validation rule for the service’s artifact/manifest identifier will help us to maintain a consistent and reliable service environment. If you experience an error when trying to update a service configuration, it may be due to an artifact identifier that does not match the new pattern. To fix this, simply update the identifier to match the pattern and save the updated configuration.