Azure / Azure/azure-rest-api-specs

[BUG] ExpressRoute CrossConnection Azure Ports not writable

Open
#31,497 2 comments 0 reactions 1 assignee Claimed by @GuptaVertika View on GitHub
bug customer-reported Mgmt question
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
2d 22h
Merged PRs (30d)
444

Description

### 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_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.