Skip to content

[Python] TypeSpec migration for azure-mgmt-cdn#46978

Draft
msyyc wants to merge 3 commits into
Azure:mainfrom
msyyc:sdk-azure-mgmt-cdn
Draft

[Python] TypeSpec migration for azure-mgmt-cdn#46978
msyyc wants to merge 3 commits into
Azure:mainfrom
msyyc:sdk-azure-mgmt-cdn

Conversation

@msyyc
Copy link
Copy Markdown
Member

@msyyc msyyc commented May 19, 2026

[Python] TypeSpec migration for azure-mgmt-cdn

This draft PR contains the regenerated azure-mgmt-cdn SDK output from the TypeSpec migration of the CDN service, along with the breaking-change analysis used to design the mitigations.

Spec source

Spec mitigation PR

Azure/azure-rest-api-specs#43333

Summary of breaking-change classifications

Category Count Action
Client name CdnManagementClient 1 MITIGATE (@@clientName)
PolicySettingsDefaultCustomBlockResponseStatusCode numeric members → ENUM_* 5 MITIGATE (@@clientName)
Multi-level flattening removal (resource model properties nesting) ~140 ACCEPT (guide §11)
Pageable list models removed 3 ACCEPT (guide §8)
Unreferenced models removed 6 ACCEPT (guide §7)
LogAnalyticsOperations parameters changed to keyword-only ~30 ACCEPT (guide §9)

Mitigated breaking changes

After the spec mitigation PR is merged, the following changelog items will no longer appear:

  • Deleted or renamed client CdnManagementClient
  • Deleted or renamed enum value PolicySettingsDefaultCustomBlockResponseStatusCode.TWO_HUNDRED
  • Deleted or renamed enum value PolicySettingsDefaultCustomBlockResponseStatusCode.FOUR_HUNDRED_THREE
  • Deleted or renamed enum value PolicySettingsDefaultCustomBlockResponseStatusCode.FOUR_HUNDRED_FIVE
  • Deleted or renamed enum value PolicySettingsDefaultCustomBlockResponseStatusCode.FOUR_HUNDRED_SIX
  • Deleted or renamed enum value PolicySettingsDefaultCustomBlockResponseStatusCode.FOUR_HUNDRED_TWENTY_NINE

Accepted breaking changes (will remain)

Per the SDK breaking-changes guide for TypeSpec migration, these changes are intentional and follow the new model-hierarchy / API-design rules:

Multi-level flattening removal (guide §11)

Flattened properties on the following models now nest under .properties:
AFDDomain, AFDDomainUpdateParameters, AFDEndpoint, AFDEndpointUpdateParameters, AFDOrigin, AFDOriginUpdateParameters, AFDOriginGroup, AFDOriginGroupUpdateParameters, CanMigrateResult, CustomDomainParameters, Endpoint, EndpointUpdateParameters, Operation, Origin, OriginUpdateParameters, OriginGroup, OriginGroupUpdateParameters, ProfileUpdateParameters, Route, RouteUpdateParameters, Rule, RuleUpdateParameters, RuleSet, Secret, SecurityPolicy, SecurityPolicyUpdateParameters.

Removed models (guide §7 / §8)

  • Pageable list wrappers: CdnWebApplicationFirewallPolicyList, ManagedRuleSetDefinitionList, EdgenodeResult.
  • Unreferenced / replaced models: AzureFirstPartyManagedCertificate, Certificate, CustomerCertificate, ManagedCertificate, ValidationToken, DeliveryRuleActionEnum (replaced by enum DeliveryRuleActionName).

Keyword-only parameters (guide §9)

All query/header parameters on LogAnalyticsOperations.get_log_analytics_metrics, get_log_analytics_rankings, get_waf_log_analytics_metrics, and get_waf_log_analytics_rankings are now keyword-only. Users should switch positional calls to keyword form.

Notes

  • This SDK output was regenerated from the TypeSpec HEAD at eb08171f and reflects the spec before the mitigation PR is merged. After the spec PR is merged, regenerate to apply the Python @@clientName overrides and the changelog should shrink accordingly.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant