Open weikanglim opened 2 years ago
One idea is to use the RP's registered operations -- it includes displayName
for resources, but this is not the source of truth of what the user sees in Azure Portal / mobile.
Example for using RP registered operations
The real source of truth is to somehow replicate the UX asset definitions that Azure UX currently uses. It includes static translations, and also some metadata to describe how resources should be translated differently based on the resource's kind
property.
We'd need to work with the team if we consume it directly. We'd also need to verify this works for custom, user registered resource providers.
We currently have built up a limited list of static translations for ARM resource types, with dynamic translation for
Microsoft.Web/sites
which translates toFunction app
vsApp Service
depending on the resource properties.We should investigate how to provide a more comprehensive list of resource type translations. Ideally, all resource types should be translated.
_Originally posted by @weikanglim in https://github.com/Azure/azure-dev/pull/152#discussion_r929278363_