Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] MCS: Traffic manager resource identifiers need to be readable (not UUIDs) #236

Closed
sjwaight opened this issue Dec 24, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@sjwaight
Copy link
Contributor

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).

@sjwaight 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
@sjwaight sjwaight added the enhancement New feature or request label Dec 24, 2024
@zhiying-lin
Copy link
Contributor

zhiying-lin commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants