[Hub Generated] Review request for Microsoft.CostManagement to add version stable/2019-11-01 #16593

omrodrig · 2021-10-29T02:08:46Z

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.

Changelog

Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?
- new service onboarding
- new API version
- update existing version for new feature
- update existing version to fix swagger quality issue in s360
- Other, please clarify
When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.
- SDK of .NET (need service team to ensure code readiness)
- SDK of Python
- SDK of Java
- SDK of Js
- SDK of Go
- PowerShell
- CLI
- Terraform
- No refresh required for updates in this PR

Contribution checklist:

I commit to follow the Breaking Change Policy of "no breaking changes"
I have reviewed the documentation for the workflow.
Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

Applicability: ⚠️

If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs

Adding new properties

All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
- Adding a new service
- Adding new API(s)
- Adding a new API version
  -[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist

If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

Removing API(s) in a stable version
Removing properties in a stable version
Removing API version(s) in a stable version
Updating API in a stable or public preview version with Breaking Change Validation errors
Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.

Please follow the link to find more details on PR review process.

openapi-workflow-bot · 2021-10-29T02:08:48Z

Hi, @omrodrig Thanks for your PR. I am workflow bot for review process. Here are some small tips.

Please ensure to do self-check against checklists in first PR comment.

PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.

For specs comparison cross API versions, Use API Specs Comparison Report Generator

If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?

Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com

openapi-workflow-bot · 2021-10-29T02:08:49Z

[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks.

openapi-pipeline-app · 2021-10-29T02:08:50Z

Swagger Validation Report

️❌BreakingChange: 1 Errors, 0 Warnings failed [Detail]

Compared Swaggers (Based on Oad v0.9.1)
- current:stable/2019-11-01/costmanagement.json compared with base:stable/2019-11-01/costmanagement.json

Rule	Message
`❌` 1033 - RemovedProperty	The new version is missing a property found in the old version. Was 'configuration' renamed or removed? New: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2704:7 Old: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2704:7

️⚠️LintDiff: 0 Warnings warning [Detail]

Linted configuring files (Based on source branch, openapi-validator v1.10.1 , classic-openapi-validator v1.1.10 )
- cost-management/resource-manager/readme.md tag:package-2019-11
Linted configuring files (Based on target branch, openapi-validator v1.10.1 , classic-openapi-validator v1.1.10 )
- cost-management/resource-manager/readme.md tag:package-2019-11

The following errors/warnings exist before current PR submission:

Only 30 items are listed, please refer to log for more details.

Rule	Message
`❌` R4005 - UniqueXmsEnumName	Must not have duplicate name of x-ms-enum extension , make sure every x-ms-enum name unique. The duplicate x-ms-enum name: operatortype, path: $.ReportConfigComparisonExpression.properties.operator Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.exports.json#L672
`❌` R4013 - IntegerTypeMustHaveFormat	The integer type does not have a format, please add it. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L1004
`❌` R4013 - IntegerTypeMustHaveFormat	The integer type does not have a format, please add it. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L1086
`❌` R4037 - MissingTypeObject	The schema 'ReportConfigDefinition' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L1439
`❌` R4037 - MissingTypeObject	The schema 'ReportConfigTimePeriod' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L1486
`❌` R4037 - MissingTypeObject	The schema 'ReportConfigDataset' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L1505
`❌` R4037 - MissingTypeObject	The schema 'ReportConfigDatasetConfiguration' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L1555
`❌` R4037 - MissingTypeObject	The schema 'ReportConfigAggregation' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L1567
`❌` R4037 - MissingTypeObject	The schema 'ReportConfigSorting' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L1594
`❌` R4037 - MissingTypeObject	The schema 'ReportConfigGrouping' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L1614
`❌` R4037 - MissingTypeObject	The schema 'ReportConfigFilter' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L1631
`❌` R4037 - MissingTypeObject	The schema 'ReportConfigComparisonExpression' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L1680
`❌` R4037 - MissingTypeObject	The schema 'ErrorDetails' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L1997
`❌` R4037 - MissingTypeObject	The schema 'Resource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2022
`❌` R4037 - MissingTypeObject	The schema 'ProxySettingResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2051
`❌` R4037 - MissingTypeObject	The schema 'ProxyResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2078
`❌` R4037 - MissingTypeObject	The schema 'DismissAlertPayload' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2455
`❌` R4037 - MissingTypeObject	The schema 'OperationListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2532
`❌` R4037 - MissingTypeObject	The schema 'display' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2559
`❌` R4037 - MissingTypeObject	The schema 'ForecastDefinition' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2581
`❌` R4037 - MissingTypeObject	The schema 'QueryDefinition' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2636
`❌` R4037 - MissingTypeObject	The schema 'QueryTimePeriod' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2683
`❌` R4037 - MissingTypeObject	The schema 'QueryDataset' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2702
`❌` R4037 - MissingTypeObject	The schema 'Status' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2740
`❌` R4037 - MissingTypeObject	The schema 'OperationStatus' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2758
`❌` R4037 - MissingTypeObject	The schema 'ReportURL' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2773
`❌` R4037 - MissingTypeObject	The schema 'QueryDatasetConfiguration' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2787
`❌` R4037 - MissingTypeObject	The schema 'QueryAggregation' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2799
`❌` R4037 - MissingTypeObject	The schema 'QueryGrouping' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2826
`❌` R4037 - MissingTypeObject	The schema 'QueryFilter' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.CostManagement/stable/2019-11-01/costmanagement.json#L2843

️️✔️Avocado succeeded [Detail] [Expand]

Validation passes for Avocado.

️️✔️ModelValidation succeeded [Detail] [Expand]

Validation passes for ModelValidation.

️️✔️SemanticValidation succeeded [Detail] [Expand]

Validation passes for SemanticValidation.

️️✔️Cross-Version Breaking Changes succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️CredScan succeeded [Detail] [Expand]

There is no credential detected.

️️✔️[Staging] SDK Track2 Validation succeeded [Detail] [Expand]

Validation passes for SDKTrack2Validation

The following tags are being changed in this PR

cost-management/resource-manager/readme.md#package-2019-11

️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]

Validation passes for PrettierCheck.

️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]

Validation passes for SpellCheck.

️️✔️[Staging] Lint(RPaaS) succeeded [Detail] [Expand]

Validation passes for Lint(RPaaS).

_{Posted by Swagger Pipeline | How to fix these errors?}

openapi-pipeline-app · 2021-10-29T02:08:50Z

Swagger Generation Artifacts

️️✔️[Staging] ApiDocPreview succeeded [Detail] [Expand]

 Please click here to preview with your @microsoft account.

️❌[Staging] SDK Breaking Change Tracking failed [Detail]

Breaking Changes Tracking

❌azure-sdk-for-python-track2 - track2_azure-mgmt-costmanagement - 3.0.0

-	Model Alert no longer has parameter tags

️✔️azure-sdk-for-go - costmanagement/mgmt/2021-01-01/costmanagement - v59.0.0
️✔️azure-sdk-for-go - costmanagement/mgmt/2020-06-01/costmanagement - v59.0.0
️✔️azure-sdk-for-go - costmanagement/mgmt/2019-11-01/costmanagement - v59.0.0
️✔️azure-sdk-for-go - costmanagement/mgmt/2019-10-01/costmanagement - v59.0.0
️✔️azure-sdk-for-go - costmanagement/mgmt/2019-01-01/costmanagement - v59.0.0
️✔️azure-sdk-for-go - costmanagement/mgmt/2018-05-31/costmanagement - v59.0.0
️✔️azure-sdk-for-go - preview/costmanagement/mgmt/2019-03-01/costmanagement - v59.0.0
️✔️azure-sdk-for-go - preview/costmanagement/mgmt/2018-08-01-preview/costmanagement - v59.0.0

️️✔️ azure-sdk-for-net succeeded [Detail] [Expand]

️✔️Succeeded [Logs]Release - Generate from 4abc028. SDK Automation 14.0.0

warn	Skip initScript due to not configured
command	sudo apt-get install -y dotnet-sdk-5.0
command	autorest --version=V2 --csharp --reflect-api-versions --license-header=MICROSOFT_MIT_NO_VERSION --use=@microsoft.azure/autorest.csharp@2.3.82 --csharp-sdks-folder=/home/vsts/work/1/s/azure-sdk-for-net/sdk ../azure-rest-api-specs/specification/cost-management/resource-manager/readme.md
cmderr	[Autorest] realpath(): Permission denied
cmderr	[Autorest] realpath(): Permission denied
cmderr	[Autorest] realpath(): Permission denied
cmderr	[Autorest] realpath(): Permission denied
cmderr	[Autorest] realpath(): Permission denied
cmderr	[Autorest] realpath(): Permission denied

️✔️Microsoft.Azure.Management.CostManagement [View full logs] [Release SDK Changes]
- Microsoft.Azure.Management.CostManagement.0.9.0-preview.nupkg
- Microsoft.Azure.Management.CostManagement.0.9.0-preview.symbols.nupkg

️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]

️✔️Succeeded [Logs]Release - Generate from 4abc028. SDK Automation 14.0.0

command	sh ./eng/initScript.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
command	generator automation ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json

️✔️costmanagement/mgmt/2021-01-01/costmanagement [View full logs] [Release SDK Changes]
```
info	[Changelog] This is a new package
```
️✔️costmanagement/mgmt/2020-06-01/costmanagement [View full logs]
```
info	[Changelog] No exported changes
```
️✔️costmanagement/mgmt/2019-11-01/costmanagement [View full logs]
```
info	[Changelog] No exported changes
```
️✔️costmanagement/mgmt/2019-10-01/costmanagement [View full logs]
```
info	[Changelog] No exported changes
```
️✔️costmanagement/mgmt/2019-01-01/costmanagement [View full logs]
```
info	[Changelog] No exported changes
```
️✔️costmanagement/mgmt/2018-05-31/costmanagement [View full logs]
```
info	[Changelog] No exported changes
```
️✔️preview/costmanagement/mgmt/2019-03-01/costmanagement [View full logs]
```
info	[Changelog] No exported changes
```
️✔️preview/costmanagement/mgmt/2018-08-01-preview/costmanagement [View full logs]
```
info	[Changelog] No exported changes
```

️⚠️ azure-sdk-for-python-track2 warning [Detail]

⚠️Warning [Logs]Release - Generate from 4abc028. SDK Automation 14.0.0

command	sh scripts/automation_init.sh ../azure-sdk-for-python_tmp/initInput.json ../azure-sdk-for-python_tmp/initOutput.json
cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json

️✔️track2_azure-mgmt-costmanagement [View full logs] [Release SDK Changes] Breaking Change Detected

info	[Changelog] **Features**
info	[Changelog]
info	[Changelog]   - Model QueryFilter has a new parameter dimension
info	[Changelog]   - Model QueryFilter has a new parameter tag
info	[Changelog]   - Model QueryFilter has a new parameter not_property
info	[Changelog]   - Model Alert has a new parameter e_tag
info	[Changelog]   - Model Export has a new parameter next_run_time_estimate
info	[Changelog]   - Model Export has a new parameter partition_data
info	[Changelog]   - Model Export has a new parameter run_history
info	[Changelog]   - Model CommonExportProperties has a new parameter next_run_time_estimate
info	[Changelog]   - Model CommonExportProperties has a new parameter partition_data
info	[Changelog]   - Model CommonExportProperties has a new parameter run_history
info	[Changelog]   - Model ExportExecution has a new parameter e_tag
info	[Changelog]   - Model ExportExecution has a new parameter error
info	[Changelog]   - Model ExportProperties has a new parameter next_run_time_estimate
info	[Changelog]   - Model ExportProperties has a new parameter partition_data
info	[Changelog]   - Model ExportProperties has a new parameter run_history
info	[Changelog]   - Model View has a new parameter dataset
info	[Changelog]   - Model ReportConfigFilter has a new parameter dimension
info	[Changelog]   - Model ReportConfigFilter has a new parameter tag
info	[Changelog]   - Model ReportConfigFilter has a new parameter not_property
info	[Changelog]   - Model ExportDeliveryDestination has a new parameter sas_token
info	[Changelog]   - Model ExportDeliveryDestination has a new parameter storage_account
info	[Changelog]   - Added operation group GenerateDetailedCostReportOperations
info	[Changelog]   - Added operation group GenerateDetailedCostReportOperationResultsOperations
info	[Changelog]   - Added operation group GenerateDetailedCostReportOperationStatusOperations
info	[Changelog]
info	[Changelog] **Breaking changes**
info	[Changelog]
info	[Changelog]   - Operation ExportsOperations.get has a new signature
info	[Changelog]   - Operation ExportsOperations.list has a new signature
info	[Changelog]   - Model QueryFilter no longer has parameter dimensions
info	[Changelog]   - Model QueryFilter no longer has parameter tags
info	[Changelog]   - Model QueryResult no longer has parameter e_tag
info	[Changelog]   - Model QueryResult no longer has parameter sku
info	[Changelog]   - Model QueryResult no longer has parameter location
info	[Changelog]   - Model Alert no longer has parameter tags
info	[Changelog]   - Model ExportExecution no longer has parameter tags
info	[Changelog]   - Model View no longer has parameter data_set
info	[Changelog]   - Model View no longer has parameter include_monetary_commitment
info	[Changelog]   - Model View no longer has parameter currency
info	[Changelog]   - Model View no longer has parameter date_range
info	[Changelog]   - Model ReportConfigFilter no longer has parameter tag_key
info	[Changelog]   - Model ReportConfigFilter no longer has parameter dimensions
info	[Changelog]   - Model ReportConfigFilter no longer has parameter tag_value
info	[Changelog]   - Model ReportConfigFilter no longer has parameter tags
info	[Changelog]   - Removed operation group GenerateReservationDetailsReportOperations
info	[Changelog]   - Removed operation group SettingsOperations

️⚠️ azure-resource-manager-schemas warning [Detail]

⚠️Warning [Logs]Release - Generate from 4abc028. Schema Automation 14.0.0

command	.sdkauto/initScript.sh ../azure-resource-manager-schemas_tmp/initInput.json ../azure-resource-manager-schemas_tmp/initOutput.json
cmderr	[initScript.sh] WARN old lockfile
cmderr	[initScript.sh] npm WARN old lockfile The package-lock.json file was created with an old version of npm,
cmderr	[initScript.sh] npm WARN old lockfile so supplemental metadata must be fetched from the registry.
cmderr	[initScript.sh] npm WARN old lockfile
cmderr	[initScript.sh] npm WARN old lockfile This is a one-time fix-up, please be patient...
cmderr	[initScript.sh] npm WARN old lockfile
warn	File azure-resource-manager-schemas_tmp/initOutput.json not found to read
command	.sdkauto/generateScript.sh ../azure-resource-manager-schemas_tmp/generateInput.json ../azure-resource-manager-schemas_tmp/generateOutput.json
cmderr	[generateScript.sh] (node:2580) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, unlink '/home/vsts/work/1/s/azure-resource-manager-schemas/schemas/2018-08-01-preview/Microsoft.CostManagement.json'
cmderr	[generateScript.sh] (Use `node --trace-warnings ...` to show where the warning was created)
cmderr	[generateScript.sh] (node:2580) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
cmderr	[generateScript.sh] (node:2580) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
cmderr	[generateScript.sh] (node:2580) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, unlink '/home/vsts/work/1/s/azure-resource-manager-schemas/schemas/2019-10-01/Microsoft.CostManagement.json'
cmderr	[generateScript.sh] (node:2580) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
warn	No file changes detected after generation

️✔️cost-management [View full logs]

_{Posted by Swagger Pipeline | How to fix these errors?}

openapi-workflow-bot · 2021-10-29T02:10:53Z

Hi @omrodrig, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review.
Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
If you want to know the production traffic statistic, please see ARM Traffic statistic.
If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback.

omrodrig · 2021-10-29T04:52:47Z

This change I made is actually fixing an error in the document as shown here: #14572. The property I removed is a property that is being passed as a required parameter in the request. When that is not true. This property isn't a required property. It's not used in the request at all. Only in the response. For this reason, I have removed it from the request. For this reason, it is not a true breaking change.

Removed field that is not used in the request

7bc4396

openapi-pipeline-app bot added the BreakingChangeReviewRequired label Oct 29, 2021

openapi-sdkautomation bot mentioned this pull request Oct 29, 2021

[AutoPR track2_azure-mgmt-costmanagement] [Hub Generated] Review request for Microsoft.CostManagement to add version stable/2019-11-01 AzureSDKAutomation/azure-sdk-for-python#7943

Closed

openapi-pipeline-app bot added the CI-BreakingChange-Python-Track2 label Oct 29, 2021

openapi-sdkautomation bot mentioned this pull request Oct 29, 2021

[AutoPR Microsoft.Azure.Management.CostManagement] [Hub Generated] Review request for Microsoft.CostManagement to add version stable/2019-11-01 AzureSDKAutomation/azure-sdk-for-net#6465

Closed

openapi-workflow-bot bot added the FixS360 label Oct 29, 2021

omrodrig marked this pull request as ready for review October 29, 2021 03:25

openapi-assignment-bot bot assigned changlong-liu Oct 29, 2021

JeffreyRichter added the Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 label Nov 6, 2021

changlong-liu approved these changes Nov 9, 2021

View reviewed changes

changlong-liu merged commit 4abc028 into Azure:main Nov 9, 2021

LeiWang3 pushed a commit to LeiWang3/azure-rest-api-specs that referenced this pull request Mar 31, 2022

Removed field that is not used in the request (Azure#16593)

99291a1

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Hub Generated] Review request for Microsoft.CostManagement to add version stable/2019-11-01 #16593

[Hub Generated] Review request for Microsoft.CostManagement to add version stable/2019-11-01 #16593

omrodrig commented Oct 29, 2021 •

edited

Loading

openapi-workflow-bot bot commented Oct 29, 2021

openapi-workflow-bot bot commented Oct 29, 2021

openapi-pipeline-app bot commented Oct 29, 2021 •

edited

Loading

openapi-pipeline-app bot commented Oct 29, 2021 •

edited

Loading

Breaking Changes Tracking

openapi-workflow-bot bot commented Oct 29, 2021

omrodrig commented Oct 29, 2021 •

edited

Loading

[Hub Generated] Review request for Microsoft.CostManagement to add version stable/2019-11-01 #16593

[Hub Generated] Review request for Microsoft.CostManagement to add version stable/2019-11-01 #16593

Conversation

omrodrig commented Oct 29, 2021 • edited Loading

Changelog

Contribution checklist:

ARM API Review Checklist

Breaking Change Review Checklist

openapi-workflow-bot bot commented Oct 29, 2021

openapi-workflow-bot bot commented Oct 29, 2021

openapi-pipeline-app bot commented Oct 29, 2021 • edited Loading

Swagger Validation Report

openapi-pipeline-app bot commented Oct 29, 2021 • edited Loading

Swagger Generation Artifacts

Breaking Changes Tracking

openapi-workflow-bot bot commented Oct 29, 2021

omrodrig commented Oct 29, 2021 • edited Loading

omrodrig commented Oct 29, 2021 •

edited

Loading

openapi-pipeline-app bot commented Oct 29, 2021 •

edited

Loading

openapi-pipeline-app bot commented Oct 29, 2021 •

edited

Loading

omrodrig commented Oct 29, 2021 •

edited

Loading