Minor fix on billingBeneifts

[gaoyp830]

ARM API Information (Control Plane)

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.

Changelog

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

1. 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

, API version update for previous endpoints as the second commit, and new API endpoint as the third commit.

2. 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.
3. When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
4. By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

• 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 the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

  • 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. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

• 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 you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.

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

NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)

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

[openapi-workflow-bot]

Hi, @gaoyp830 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. vscswagger@microsoft.com

[openapi-pipeline-app]

Swagger Validation Report

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

compared swaggers (via Oad v0.10.2)]	new version	base version
billingbenefits.json	2022-11-01(beec011)	2022-11-01(main)

Rule	Message
❌ 1006 - RemovedDefinition	The new version is missing a definition that was found in the old version. Was 'BenefitTerm' removed or renamed? New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L675:3 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L672:3
❌ 1008 - ModifiedOperationId	The operation id has been changed from 'SavingsPlansInOrder_List' to 'SavingsPlan_List'. This will impact generated code. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L289:7 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L286:7
❌ 1008 - ModifiedOperationId	The operation id has been changed from 'SavingsPlans_List' to 'SavingsPlan_ListAll'. This will impact generated code. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L328:7 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L325:7
❌ 1008 - ModifiedOperationId	The operation id has been changed from 'SavingsPlanUpdate_Validate' to 'SavingsPlan_ValidateUpdate'. This will impact generated code. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L503:7 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L500:7
❌ 1008 - ModifiedOperationId	The operation id has been changed from 'SavingsPlanPurchase_Validate' to 'ValidatePurchase'. This will impact generated code. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L545:7 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L542:7
❌ 1017 - ReferenceRedirection	The '$ref' property points to different models in the old and new versions. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L96:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L93:9
❌ 1017 - ReferenceRedirection	The '$ref' property points to different models in the old and new versions. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1207:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1204:9
❌ 1017 - ReferenceRedirection	The '$ref' property points to different models in the old and new versions. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1096:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1093:9
❌ 1017 - ReferenceRedirection	The '$ref' property points to different models in the old and new versions. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1486:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1483:9
❌ 1017 - ReferenceRedirection	The '$ref' property points to different models in the old and new versions. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L596:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L593:9
❌ 1017 - ReferenceRedirection	The '$ref' property points to different models in the old and new versions. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1728:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1725:9
❌ 1017 - ReferenceRedirection	The '$ref' property points to different models in the old and new versions. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L732:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L729:9
❌ 1017 - ReferenceRedirection	The '$ref' property points to different models in the old and new versions. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1641:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1638:9
❌ 1019 - RemovedEnumValue	The new version is removing enum value(s) 'ComputeSavingsPlan' from the old version. Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L593:9
❌ 1019 - RemovedEnumValue	The new version is removing enum value(s) 'ComputeSavingsPlan' from the old version. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1748:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1745:9
❌ 1019 - RemovedEnumValue	The new version is removing enum value(s) 'ComputeSavingsPlan' from the old version. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L768:5 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L765:5
❌ 1047 - XmsEnumChanged	The new version has a different x-ms-enum 'name' than the previous one. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L96:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L93:9
❌ 1047 - XmsEnumChanged	The new version has a different x-ms-enum 'name' than the previous one. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1207:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1204:9
❌ 1047 - XmsEnumChanged	The new version has a different x-ms-enum 'name' than the previous one. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1096:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1093:9
❌ 1047 - XmsEnumChanged	The new version has a different x-ms-enum 'name' than the previous one. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1486:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1483:9
❌ 1047 - XmsEnumChanged	The new version has a different x-ms-enum 'name' than the previous one. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L596:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L593:9
❌ 1047 - XmsEnumChanged	The new version has a different x-ms-enum 'name' than the previous one. New: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1728:9 Old: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1725:9

️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]

There are no breaking changes.

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

There is no credential detected.

️⚠️LintDiff: 0 Warnings warning [Detail]

compared tags (via openapi-validator v2.0.0)	new version	base version
package-2022-11-01	package-2022-11-01(beec011)	package-2022-11-01(main)

The following errors/warnings exist before current PR submission:

Rule	Message
⚠️ LroExtension	Operations with a 202 response should specify x-ms-long-running-operation: true. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L449
⚠️ PutRequestResponseScheme	A PUT operation request body schema should be the same as its 200 response schema, to allow reusing the same entity between GET and PUT. If the schema of the PUT request body is a superset of the GET response body, make sure you have a PATCH operation to make the resource updatable. Operation: 'ReservationOrderAlias_Create' Request Model: 'parameters[2].schema' Response Model: 'responses[200].schema' Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L581
⚠️ EnumInsteadOfBoolean	Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L902
⚠️ SchemaDescriptionOrTitle	Schema should have a description or title. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1003
⚠️ SchemaDescriptionOrTitle	Schema should have a description or title. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1030
⚠️ SchemaDescriptionOrTitle	Schema should have a description or title. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1147
⚠️ AvoidNestedProperties	Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1237
⚠️ SchemaDescriptionOrTitle	Schema should have a description or title. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1263
⚠️ SchemaDescriptionOrTitle	Schema should have a description or title. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1351
⚠️ SchemaDescriptionOrTitle	Schema should have a description or title. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1373
⚠️ SchemaDescriptionOrTitle	Schema should have a description or title. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1381
⚠️ SchemaDescriptionOrTitle	Schema should have a description or title. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1392
⚠️ SchemaDescriptionOrTitle	Schema should have a description or title. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1404
⚠️ EnumInsteadOfBoolean	Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1424
⚠️ SchemaDescriptionOrTitle	Schema should have a description or title. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1438
⚠️ SchemaDescriptionOrTitle	Schema should have a description or title. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1464
⚠️ SchemaDescriptionOrTitle	Schema should have a description or title. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1476
⚠️ LocationMustHaveXmsMutability	Property location must have 'x-ms-mutability':['read', 'create'] extension defined. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1619
⚠️ LocationMustHaveXmsMutability	Property location must have 'x-ms-mutability':['read', 'create'] extension defined. Location: Microsoft.BillingBenefits/stable/2022-11-01/billingbenefits.json#L1698

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

Validation passes for Avocado.

️️✔️ApiReadinessCheck succeeded [Detail] [Expand]

️⚠️~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]

API Test is not triggered due to precheck failure. Check pipeline log for details.

️️✔️~[Staging] SwaggerAPIView succeeded [Detail] [Expand]

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

Validation passes for ModelValidation.

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

Validation passes for SemanticValidation.

️️✔️PoliCheck succeeded [Detail] [Expand]

Validation passed for PoliCheck.

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

Validation passes for PrettierCheck.

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

Validation passes for SpellCheck.

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

Validation passes for Lint(RPaaS).

️️✔️CadlValidation succeeded [Detail] [Expand]

Validation passes for CadlValidation.

️️✔️PR Summary succeeded [Detail] [Expand]

Validation passes for Summary.

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

[openapi-pipeline-app]

Swagger Generation Artifacts

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

 Please click here to preview with your @microsoft account. 

️️✔️SDK Breaking Change Tracking succeeded [Detail] [Expand]

Breaking Changes Tracking

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

• ⚠️Warning [Logs]Release - Generate from 7d98899. 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
  cmderr	[automation_generate.sh]
  cmderr	[automation_generate.sh] npm notice New major version of npm available! 8.19.2 -> 9.1.2
  cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.1.2>
  cmderr	[automation_generate.sh] npm notice Run `npm install -g npm@9.1.2` to update!
  cmderr	[automation_generate.sh] npm notice

• ️✔️track2_azure-mgmt-billingbenefits [View full logs]  [Release SDK Changes]
  • azure_mgmt_billingbenefits-1.0.0b1-py3-none-any.whl
  • azure-mgmt-billingbenefits-1.0.0b1.zip

  info	[Changelog]   - Initial Release

️⚠️ azure-sdk-for-java warning [Detail]

• ⚠️Warning [Logs]Release - Generate from 7d98899. SDK Automation 14.0.0

  command	./eng/mgmt/automation/init.sh ../azure-sdk-for-java_tmp/initInput.json ../azure-sdk-for-java_tmp/initOutput.json
  cmderr	[init.sh] [notice] A new release of pip available: 22.3 -> 22.3.1
  cmderr	[init.sh] [notice] To update, run: pip install --upgrade pip
  cmderr	[init.sh] [notice] A new release of pip available: 22.3 -> 22.3.1
  cmderr	[init.sh] [notice] To update, run: pip install --upgrade pip
  command	./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json

• ️✔️azure-resourcemanager-billingbenefits [View full logs]  [Release SDK Changes]
  • pom.xml
  • azure-resourcemanager-billingbenefits-1.0.0-beta.1.jar
  • azure-resourcemanager-billingbenefits-1.0.0-beta.1-sources.jar

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

• ️✔️Succeeded [Logs]Release - Generate from 7d98899. SDK Automation 14.0.0

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

• ️✔️sdk/resourcemanager/billingbenefits/armbillingbenefits [View full logs]  [Release SDK Changes]

  info	[Changelog] This is a new package
  info	[Changelog]

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

• ️✔️Succeeded [Logs]Release - Generate from 7d98899. SDK Automation 14.0.0

  command	sh .scripts/automation_init.sh ../azure-sdk-for-js_tmp/initInput.json ../azure-sdk-for-js_tmp/initOutput.json
  warn	File azure-sdk-for-js_tmp/initOutput.json not found to read
  command	sh .scripts/automation_generate.sh ../azure-sdk-for-js_tmp/generateInput.json ../azure-sdk-for-js_tmp/generateOutput.json

• ️✔️@azure/arm-billingbenefits [View full logs]  [Release SDK Changes]
  • azure-arm-billingbenefits-1.0.0.tgz

  info	[Changelog]
  error	breakingChangeTracking is enabled, but version or changelogItem is not found in output.

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

• ⚠️Warning [Logs]Release - Generate from 7d98899. 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] 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

• ️✔️billingbenefits [View full logs]  [Release Schema Changes]

️️✔️ azure-powershell succeeded [Detail] [Expand]

• ️✔️Succeeded [Logs]Release - Generate from 7d98899. SDK Automation 14.0.0

  command	sh ./tools/SwaggerCI/init.sh ../azure-powershell_tmp/initInput.json ../azure-powershell_tmp/initOutput.json
  command	pwsh ./tools/SwaggerCI/psci.ps1 ../azure-powershell_tmp/generateInput.json ../azure-powershell_tmp/generateOutput.json

• ️✔️Az.BillingBenefitsRp [View full logs]  [Release SDK Changes]
  • Az.BillingBenefitsRp.0.1.0.nupkg

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

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/billingbenefits/armbillingbenefits	Create ApiView failed. Please ensure your github account in Azure/Microsoft is public and add a comment "/azp run" to re-trigger the CI.
Python	track2_azure-mgmt-billingbenefits	Create ApiView failed. Please ensure your github account in Azure/Microsoft is public and add a comment "/azp run" to re-trigger the CI.
Java	azure-resourcemanager-billingbenefits	Create ApiView failed. Please ensure your github account in Azure/Microsoft is public and add a comment "/azp run" to re-trigger the CI.
JavaScript	@azure/arm-billingbenefits	Create ApiView failed. Please ensure your github account in Azure/Microsoft is public and add a comment "/azp run" to re-trigger the CI.

[openapi-workflow-bot]

Hi, @gaoyp830 your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com).

[openapi-workflow-bot]

Hi @gaoyp830, 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.
Note: To avoid breaking change, you can refer to Shift Left Solution for detecting breaking change in early phase at your service code repository.

[ruowan]

There are breaking changes detected. Is there any SDK released? Any customer impact?

[TimLovellSmith]

[TimLovellSmith]

Signing off for ARM. Breaking Changes review is required though.