[Python] TypeSpec migration for azure-mgmt-managednetworkfabric#47388
Closed
msyyc wants to merge 6 commits into
Closed
[Python] TypeSpec migration for azure-mgmt-managednetworkfabric#47388msyyc wants to merge 6 commits into
msyyc wants to merge 6 commits into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TypeSpec migration breaking-change analysis —
azure-mgmt-managednetworkfabricSpec source
2025-07-15(latest in TypeSpec enum Versions; the swagger default tag's2023-06-15is not present in the TypeSpecenum Versions)Spec mitigation PR
Classification summary
Mitigated (4 model renames restored via
@@clientName... "python")ManagementNetworkPatchConfigurationManagementNetworkConfigurationPatchablePropertiesTerminalServerPatchConfigurationNetworkFabricPatchablePropertiesTerminalServerConfigurationVpnOptionAPropertiesOptionAPropertiesVpnOptionBPropertiesOptionBPropertiesAccepted breaking changes (no mitigation)
These remain in the SDK as genuine, non-mitigable changes:
Model X deleted or renamed its instance variable Yentries — properties now live under the actual REST hierarchy (e.g. under.properties). This is required TypeSpec behavior.*Listmodel removals (Cat 8):ExternalNetworksList,InternalNetworksList,NetworkInterfacesList,NetworkToNetworkInterconnectsList.*PatchablePropertiesfamily,ExtendedLocation,ExtensionEnumProperty,IpCommunity*OperationProperties,IpExtendedCommunity*OperationProperties,OptionAProperties-adjacent vpn config wrappers,NetworkToNetworkInterconnectPropertiesOptionBLayer3Configuration(a thin subclass alias over the still-existingOptionBLayer3Configuration),NetworkTap*DestinationsItem,PollingIntervalInSeconds, etc.begin_*LRO methods now return the 2025-07-15 response types (e.g.UpdateAdministrativeStateResponse,OperationStatusResult,NetworkDeviceUpgradeResponse, ...) instead of the old sharedCommonPostActionResponseFor*types, which no longer exist in the new API. No clean mitigation is possible.See
CHANGELOG.mdfor the full per-item list.