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

Maintenance API returns resource group name in lower-case #8653

Open
njuCZ opened this issue Mar 10, 2020 · 1 comment
Open

Maintenance API returns resource group name in lower-case #8653

njuCZ opened this issue Mar 10, 2020 · 1 comment
Labels
Maintenance Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@njuCZ
Copy link
Contributor

njuCZ commented Mar 10, 2020

We've been working with version 2018-06-01-preview of the Maintenance API's (via v38.1.0 of the Azure SDK for Go) - and have noticed a bug where the Resource Group name that's returned from Azure is always lower-cased for the ID, regardless of the input case. For example if I create a Maintenance Configuration in the resource group Group1 the ID for create will be:

/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/group1/providers/microsoft.maintenance/maintenanceconfigurations/mc1

when actually this should be:

/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/Group1/providers/microsoft.maintenance/maintenanceconfigurations/mc1

Would it be possible to update this API to return the Resource Group name in the correct case, rather than lower-casing it?

Thanks!

@akning-ms akning-ms added Service Attention Workflow: This issue is responsible by Azure service team. triage labels Mar 12, 2020
@akning-ms
Copy link
Contributor

@shants123 for reassign if need. or let me know if you are not right contact person. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants