You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When interacting with TrafficManagerBackend or TrafficManagerProfile CRs any references to Traffic Manager instances should use human readable Traffic Manager resource names and not render resource IDs (UUIDs).
The text was updated successfully, but these errors were encountered:
sjwaight
changed the title
[Feature] Traffic manager resource identifiers need to be readable (not UUIDs)
[Feature] MCS: Traffic manager resource identifiers need to be readable (not UUIDs)
Dec 24, 2024
The reason of using uuid is to solve the name conflict issue, especially when we introduce BYO resource group/profile. The atm resources are supposed to be managed by our controllers, instead of human. For easier debugging/troubleshooting, it should be addressed in #237 to use the azure resource id returned in the status.
Discussed with @circy9 and agreed on keeping the current behavior.
When interacting with TrafficManagerBackend or TrafficManagerProfile CRs any references to Traffic Manager instances should use human readable Traffic Manager resource names and not render resource IDs (UUIDs).
The text was updated successfully, but these errors were encountered: