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.

Sign up for GitHub

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

Jump to bottom

[BUG] ExpressRoute CrossConnection Azure Ports not writable #31497

Open
tomfrenzel opened this issue Nov 11, 2024 · 1 comment
Open

[BUG] ExpressRoute CrossConnection Azure Ports not writable #31497

tomfrenzel opened this issue Nov 11, 2024 · 1 comment
Assignees
@GuptaVertika
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@tomfrenzel
Copy link

API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/network/resource-manager/Microsoft.Network/stable/2024-03-01/expressRouteCrossConnection.json

API Spec version

2024-03-01

Describe the bug

As stated inside the ExpressRoute documentation, it should be possible to change the PrimaryAzurePort and SecondaryAzurePort of a ExpressRoute CrossConnection.
Although, they are defined as read-only

See: https://learn.microsoft.com/en-us/azure/expressroute/circuit-placement-api#move-a-target-expressroute-circuit-to-a-specific-port-pair

This is especcially a problem when using the Azure SDK for .NET since there is no way to change the Ports without the properties being writable.

I already created the PR #31478 for this but i am not sure if people outside Microsoft are allowd to merge changes into this repo.

Expected behavior

The PrimaryAzurePort and SecondaryAzurePort of a ExpressRoute CrossConnection should be writable.

Actual behavior

The PrimaryAzurePort and SecondaryAzurePort of a ExpressRoute CrossConnection are readonly.

Reproduction Steps

Look at the API Spec. There the properties are set to read-only.

Environment

No response
@tomfrenzel tomfrenzel added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Nov 11, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Nov 11, 2024
@v-jiaodi v-jiaodi added the Mgmt This issue is related to a management-plane library. label Nov 12, 2024
@v-jiaodi
Copy link
Member

@GuptaVertika please help take a look, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@GuptaVertika GuptaVertika

Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tomfrenzel @v-jiaodi @GuptaVertika