[Python] TypeSpec migration for azure-mgmt-costmanagement

[msyyc]

TypeSpec migration breaking change analysis for azure-mgmt-costmanagement

• TypeSpec folder: specification/cost-management/resource-manager/Microsoft.CostManagement/CostManagement
• Pre-migration swagger source: specification/cost-management/resource-manager@79839e98
• Swagger API version: 2025-03-01 (default tag: package-2025-03)
• Generated with apiVersion: 2025-03-01 (matched from swagger default tag)

Summary of classifications

Classification	Count
ACCEPT	All detected breaking changes
MITIGATE	0

No spec mitigations were required. All breaking changes fall under accepted categories from the Breaking Changes Guide.

Accepted breaking changes (will remain)

Rule 6 — Common Types Upgrade (ACCEPT)

• Deleted models: ErrorDetailAutoGenerated, ErrorResponseAutoGenerated, ErrorResponseAutoGenerated2, OperationStatusAutoGenerated
• Return type changes for PriceSheetOperations.begin_download_by_billing_account: OperationStatusAutoGenerated → OperationStatus
• OperationStatusType.COMPLETE enum value removal (false positive — old & new both use RUNNING/COMPLETED/FAILED)

Rule 7 — Removal of Unreferenced Models (ACCEPT)

• EAPriceSheetProperties, ScheduledActionProxyResource

Rule 8 — Removal of Pageable Models (ACCEPT)

• CostAllocationRuleList

Rule 9 — Parameters Changed to Keyword-only (ACCEPT)

• Many positional_or_keyword → keyword_only changes across BenefitRecommendationsOperations, BenefitUtilizationSummariesOperations, DimensionsOperations, ExportsOperations, GenerateReservationDetailsReportOperations

Rule 10 — Removal of if_match (ACCEPT)

• ScheduledActionsOperations.create_or_update and create_or_update_by_scope: if_match removed, etag/match_condition added

Rule 11 — Removal of Multi-level Flattened Properties (ACCEPT)

• Flattened properties replaced by properties on: CostDetailsOperationResults, DismissAlertPayload, Export, ForecastResult, GenerateDetailedCostReportOperationResult, GenerateDetailedCostReportOperationStatuses, IncludedQuantityUtilizationSummary, OperationStatus, QueryResult, SavingsPlanUtilizationSummary

Rule 12 — Renamed Properties That Conflict with Base Model Methods (ACCEPT)

• .values → .values_property on: BudgetComparisonExpression, ForecastComparisonExpression, QueryComparisonExpression, ReportConfigComparisonExpression, SourceCostAllocationResource, TargetCostAllocationResource

Rule 13 — Renamed Enums (consolidated in changelog as renames)

• KpiType → KpiTypeType
• PivotType → PivotTypeType

Spec mitigation PR

None required.