Skip to content

use of "global" on resources #41617

Closed
Closed
@Klaas-

Description

@Klaas-

Describe the bug
Hi,
currently it seems that sometimes you use "Global" sometimes "global" as location. I am guessing this should be uniform everywhere.

To Reproduce
https://learn.microsoft.com/en-us/python/api/azure-mgmt-monitor/azure.mgmt.monitor.v2023_01_01.aio.operations.actiongroupsoperations?view=azure-python#azure-mgmt-monitor-v2023-01-01-aio-operations-actiongroupsoperations-get
returns
"Global"

https://learn.microsoft.com/en-us/python/api/azure-mgmt-monitor/azure.mgmt.monitor.v2020_10_01.aio.operations.activitylogalertsoperations?view=azure-python#azure-mgmt-monitor-v2020-10-01-aio-operations-activitylogalertsoperations-get
returns
"global"

for location.

Expected behavior
Consistent capitalization of a location name throughout azure. It is not important for me if at the end its either one, I just would like it to be consistently one or the other.

Metadata

Metadata

Assignees

No one assigned

    Labels

    customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions