Validate 'Display Name' for API Management's named values

[CSymes]

When creating a new Named Value through APIM in the Azure portal, an apparently undocumented naming restriction is noted regarding its display name:

When applying a plan containing a named value with a non-compliant display name, this would previously plan as valid, then fail with an ambiguous performing CreateOrUpdate: unexpected status 400 with error: ValidationError: One or more fields contain incorrect values.

[katbyte]

Thanks for this @CSymes ! LGTM 💣

[alexwiese]

@katbyte @CSymes
I’m seeing validation errors now with display names that satisfy the requirements.
wouldn’t this new regex only match a single character?

display names can be more than one character

[CSymes]

@alexwiese thanks for fixing that - not sure how that slipped through!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.