[Python] TypeSpec migration for azure-mgmt-appcontainers#47072
Draft
msyyc wants to merge 5 commits into
Draft
Conversation
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.
[Python] TypeSpec migration breaking-change analysis for
azure-mgmt-appcontainersSources
2026-01-01(default tag:package-2026-01-01)2026-01-01(matched from swagger default tag)Summary
No spec mitigation PR was created — every breaking change matched an "Accept" pattern in the SDK breaking changes guide.
Accepted breaking changes
1. Pageable list-response models removed (Guide §8)
Python no longer surfaces named
*Collection/*Resultpaging models forlistoperations. The following are removed:AuthConfigCollection,AvailableOperations,AvailableWorkloadProfilesCollection,CertificateCollection,ConnectedEnvironmentCollection,ContainerAppCollection,DaprComponentsCollection,HttpRouteConfigCollection,JavaComponentsCollection,JobExecutionNamesCollection,JobsCollection,ListUsagesResult,MaintenanceConfigurationCollection,ManagedCertificateCollection,ManagedEnvironmentsCollection,RevisionCollection,SessionPoolCollection,SourceControlCollection,WorkflowEnvelopeCollection,WorkloadProfileStatesCollectionUser impact: none — these were never user-instantiated; pagers return
ItemPaged[<T>]as before.2. Multi-level property flattening removed (Guide §11)
MaintenanceConfigurationResourcelost direct propertyscheduled_entries; access via the new nested.properties.scheduled_entries(newpropertiesproperty added, newScheduledEntriesmodel added).3. Header/query parameters → keyword-only (Guide §9)
ContainerAppsOperations.list_custom_host_name_analysis: parametercustom_hostnamechanged frompositional_or_keywordtokeyword_only.4. Enum singular rename:
ExtendedLocationTypes→ExtendedLocationTypeSame wire value (
"CustomLocation"). Mitigation via@@clientNamewas attempted but the oldExtendedLocationTypesis still referenced by@typeChangedFromin the versioned TypeSpec, causing a duplicate-client-name conflict; mitigation was reverted. Single-member enum, minimal surface, so accepted.5. Container model
__init__signature:argsparameter is nowvar_positional(*args)Affects:
BaseContainer,Container,InitContainer,JobExecutionContainer,SessionContainer.The TypeSpec emitter treats the literal property name
argsspecially (it is Python's conventional*argsname), converting it from a keyword-only list parameter into variadic positional arguments. This is an emitter convention — applies uniformly across the 5 container models and is not addressable via@@clientName/@@overridewithout renaming the wire property.Migration:
Container(args=["sh","-c"])→Container("sh","-c")(orContainer(args=...)is no longer valid).Generated artifacts
364ccc21e93449f008e8f6bbb897402f76edc6