[Python] TypeSpec migration for azure-mgmt-cdn#46978
Closed
msyyc wants to merge 12 commits into
Closed
Conversation
…into sdk-azure-mgmt-cdn
…into sdk-azure-mgmt-cdn
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:
azure-mgmt-cdnSources
2025-06-01(default tag:package-2025-06)2025-06-01(matched from swagger default tag)Breaking change classification
propertiesrestored)Certificate,CustomerCertificate,ManagedCertificate,AzureFirstPartyManagedCertificate)CdnWebApplicationFirewallPolicyList,ManagedRuleSetDefinitionList,EdgenodeResult)ValidationToken)LogAnalyticsOperationsparameters changedpositional_or_keyword→keyword_onlyTotal: All breaking changes are ACCEPT per the SDK Breaking Changes Guide. No
client.tspmitigations are required.Accepted breaking changes that will remain
Nested
propertiesaccess required (Rule 11): Properties on resource models such asAFDDomain,AFDEndpoint,AFDOrigin,AFDOriginGroup,Endpoint,Origin,OriginGroup,Route,Rule,RuleSet,Secret,SecurityPolicy,Operation, and their*UpdateParameterscounterparts must now be accessed through the nested.propertiesobject instead of directly on the resource (e.g.endpoint.host_name→endpoint.properties.host_name). The new structure mirrors the actual REST API hierarchy.Removed polymorphic certificate types:
Certificatebase class and its three derived classes (AzureFirstPartyManagedCertificate,CustomerCertificate,ManagedCertificate) are no longer exposed. Users wiring secrets should use the*Parameterstypes (CustomerCertificateParameters,ManagedCertificateParameters,AzureFirstPartyManagedCertificateParameters) which remain available.Removed pageable list models:
CdnWebApplicationFirewallPolicyList,ManagedRuleSetDefinitionList,EdgenodeResult— list operations returnItemPaged[T]directly; these wrapper types are not needed.Removed
ValidationTokenmodel — the validate-token API now returns the token value directly.LogAnalyticsOperationsquery parameters are keyword-only:get_log_analytics_metrics,get_log_analytics_rankings,get_waf_log_analytics_metrics,get_waf_log_analytics_rankings— pass parameters likemetrics=,date_time_begin=,granularity=as keyword arguments.Spec mitigation PR
None required — no MITIGATE-classified breaking changes.