Add pagination to cost management Query API

[GuillaumeColom]

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

Add "$skipToken" parameter to CostManagement Query API for pagination.
The nextLink element already exists in response and already contains the "$skipToken" parameter.
We already can send the "$skipToken" as a query parameter and it works but it doesn't appear in the API spec.

This pull request simply declares the "$skipToken" parameter in CostManagement Query API specs.
Linked to another pull request to Azure SDK for Java : Azure/azure-sdk-for-java#29381

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.

The services already works with the skipToken.

3. When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.

July 2022 (or maybe June if possible).

4. If updating an existing version, please select the specific language 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?

I don't have access to contribution documentation.

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 appy 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 are using OpenAPIHub to initialize the PR for adding a new version. 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 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]

Hi, @GuillaumeColom 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 succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️LintDiff succeeded [Detail] [Expand]

Validation passes for LintDiff.

• Linted configuring files (Based on source branch, openapi-validator v1.13.0 , classic-openapi-validator v1.2.4 )
  • cost-management/resource-manager/readme.md tag:default
• Linted configuring files (Based on target branch, openapi-validator v1.13.0 , classic-openapi-validator v1.2.4 )
  • cost-management/resource-manager/readme.md tag:default

️❌Avocado: 23 Errors, 0 Warnings failed [Detail]

Rule	Message
❌ UNREFERENCED_JSON_FILE	The swagger JSON file is not referenced from the readme file. readme: specification/cost-management/resource-manager/readme.md json: Microsoft.CostManagement/preview/2022-07-01-preview/costmanagement.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/BillingAccountQuery.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/BillingAccountQueryGrouping.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/DepartmentQuery.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/DepartmentQueryGrouping.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/EnrollmentAccountQuery.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/EnrollmentAccountQueryGrouping.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/ExternalBillingAccountsQuery.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/ExternalSubscriptionsQuery.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/MCABillingAccountQuery.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/MCABillingAccountQueryGrouping.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/MCABillingProfileQuery.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/MCABillingProfileQueryGrouping.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/MCACustomerQuery.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/MCACustomerQueryGrouping.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/MCAInvoiceSectionQuery.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/MCAInvoiceSectionQueryGrouping.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/ManagementGroupQuery.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/ManagementGroupQueryGrouping.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/ResourceGroupQuery.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/ResourceGroupQueryGrouping.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/SubscriptionQuery.json
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: specification/cost-management/resource-manager/readme.md json: preview/2022-07-01-preview/examples/SubscriptionQueryGrouping.json

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

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

Rule	Message
❌ unacceptable kind of an object to dump [object Error]	"role":"Model Validation", "url":"https://github.com/Azure/azure-rest-api-specs/blob/4b31dcb864e6d078d982ca9ba7016d82d2e76379/specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2022-07-01-preview/costmanagement.json"

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

Rule

Message

❌ INTERNAL_ERROR

Unexpected internal error: ENOENT: no such file or directory, open 'specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2022-07-01-preview/examples/PrivateViewList.json' Error: ENOENT: no such file or directory, open 'specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2022-07-01-preview/examples/PrivateViewList.json' JsonUrl: Microsoft.CostManagement/preview/2022-07-01-preview/costmanagement.json

️❌Cross-Version Breaking Changes: 2 Errors, 0 Warnings failed [Detail]

• Compared Swaggers (Based on Oad v0.9.5)
  • current:preview/2022-07-01-preview/common-types.json compared with base:stable/2021-10-01/common-types.json

The following breaking changes are detected by comparison with the latest stable version:

Rule

Message

❌ Runtime Exception

"new":"https://github.com/Azure/azure-rest-api-specs/blob/4b31dcb864e6d078d982ca9ba7016d82d2e76379/specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2022-07-01-preview/costmanagement.json", "old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cost-management/resource-manager/Microsoft.CostManagement/stable/2021-10-01/costmanagement.json", "details":"Command failed: node /mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.30/common/temp/node_modules/.pnpm/@Azure+oad@0.9.5/node_modules/autorest/dist/app.js --v2 --input-file=specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2022-07-01-preview/costmanagement.json --output-artifact=swagger-document.json --output-artifact=swagger-document.map --output-file=new --output-folder=/tmp\nERROR: Referenced file 'file:///mnt/vss/_work/1/azure-rest-api-specs/specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2022-07-01-preview/examples/OperationList.json' not found\n - file:///mnt/vss/_work/1/azure-rest-api-specs/specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2022-07-01-preview/costmanagement.json:1264:12 ($.paths["/providers/Microsoft.CostManagement/operations"].get["x-ms-examples"].OperationList["$ref"])\nFATAL: swagger-document/loader - FAILED\nFATAL: Error: [OperationAbortedException] Error occur"

The following breaking changes are detected by comparison with latest preview version:

Rule

Message

❌ Runtime Exception

"new":"https://github.com/Azure/azure-rest-api-specs/blob/4b31dcb864e6d078d982ca9ba7016d82d2e76379/specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2022-07-01-preview/costmanagement.json", "old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2019-04-01-preview/costmanagement.json", "details":"Command failed: node /mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.30/common/temp/node_modules/.pnpm/@Azure+oad@0.9.5/node_modules/autorest/dist/app.js --v2 --input-file=specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2022-07-01-preview/costmanagement.json --output-artifact=swagger-document.json --output-artifact=swagger-document.map --output-file=new --output-folder=/tmp\nERROR: Referenced file 'file:///mnt/vss/_work/1/azure-rest-api-specs/specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2022-07-01-preview/examples/OperationList.json' not found\n - file:///mnt/vss/_work/1/azure-rest-api-specs/specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2022-07-01-preview/costmanagement.json:1264:12 ($.paths["/providers/Microsoft.CostManagement/operations"].get["x-ms-examples"].OperationList["$ref"])\nFATAL: swagger-document/loader - FAILED\nFATAL: Error: [OperationAbortedException] Error occur"

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

There is no credential detected.

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

Validation passed for PoliCheck.

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

Validation passes for SDKTrack2Validation

️️✔️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).

_{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 failed [Detail]

Breaking Changes Tracking

️✔️azure-sdk-for-go - armcostmanagement - 1.0.1
❌azure-sdk-for-python-track2 - track2_azure-mgmt-costmanagement - 3.0.0

️❌ azure-sdk-for-net failed [Detail]

• ❌Failed [Logs] Generate from ce2010e7c85ca3608176c698f7350e03421d52e4. SDK Automation 14.0.0

  warn	Skip initScript due to not configured
  command	sudo apt-get install -y dotnet-sdk-6.0
  command	autorest --version=2.0.4421 --csharp --reflect-api-versions --license-header=MICROSOFT_MIT_NO_VERSION --use=@microsoft.azure/autorest.csharp@2.3.82 --csharp-sdks-folder=/mnt/vss/_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
  cmderr	[Autorest] No usable version of the libssl was found
  cmderr	[Autorest] FATAL: csharp/simplifier - FAILED
  cmderr	[Autorest] FATAL: Error: [Exception] AutoRest extension '@microsoft.azure/autorest.csharp' terminated.
  cmderr	[Autorest] Process() cancelled due to exception : [Exception] AutoRest extension '@microsoft.azure/autorest.csharp' terminated.
  error	Script return with result [failed] code [1] signal [null] cwd [azure-sdk-for-net]: autorest
  warn	Skip package processing as generation is failed

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

• ️✔️Succeeded [Logs] Generate from ce2010e7c85ca3608176c698f7350e03421d52e4. 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

• ️✔️armcostmanagement [View full logs]  [Preview SDK Changes]

  info	[Changelog] ### Other Changes
  info	[Changelog]
  info	[Changelog] Total 0 breaking change(s), 0 additive change(s).

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

• ⚠️Warning [Logs] Generate from ce2010e7c85ca3608176c698f7350e03421d52e4. 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]  config global `--global`, `--local` are deprecated. Use `--location=global` instead.

• ️✔️track2_azure-mgmt-costmanagement [View full logs]  [Preview SDK Changes] Breaking Change Detected
  • azure-mgmt-costmanagement-1.0.0b1.zip
  • azure_mgmt_costmanagement-1.0.0b1-py3-none-any.whl

  info	[Changelog] **Features**
  info	[Changelog]
  info	[Changelog]   - Added operation group GenerateDetailedCostReportOperationResultsOperations
  info	[Changelog]   - Added operation group GenerateDetailedCostReportOperationStatusOperations
  info	[Changelog]   - Added operation group GenerateDetailedCostReportOperations
  info	[Changelog]   - Model Alert has a new parameter e_tag
  info	[Changelog]   - Model AlertPropertiesDetails has a new parameter company_name
  info	[Changelog]   - Model AlertPropertiesDetails has a new parameter department_name
  info	[Changelog]   - Model AlertPropertiesDetails has a new parameter enrollment_end_date
  info	[Changelog]   - Model AlertPropertiesDetails has a new parameter enrollment_number
  info	[Changelog]   - Model AlertPropertiesDetails has a new parameter enrollment_start_date
  info	[Changelog]   - Model AlertPropertiesDetails has a new parameter invoicing_threshold
  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 Dimension has a new parameter e_tag
  info	[Changelog]   - Model Dimension has a new parameter location
  info	[Changelog]   - Model Dimension has a new parameter sku
  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 ExportDeliveryDestination has a new parameter sas_token
  info	[Changelog]   - Model ExportDeliveryDestination has a new parameter storage_account
  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 Operation has a new parameter id
  info	[Changelog]   - Model OperationDisplay has a new parameter description
  info	[Changelog]   - Model Resource has a new parameter e_tag
  info	[Changelog]   - Model Resource has a new parameter location
  info	[Changelog]   - Model Resource has a new parameter sku
  info	[Changelog]
  info	[Changelog] **Breaking changes**
  info	[Changelog]
  info	[Changelog]   - Model Alert no longer has parameter tags
  info	[Changelog]   - Model ExportExecution no longer has parameter tags
  info	[Changelog]   - Model ReportConfigFilter no longer has parameter tag_key
  info	[Changelog]   - Model ReportConfigFilter no longer has parameter tag_value
  info	[Changelog]   - Operation ExportsOperations.get has a new parameter expand
  info	[Changelog]   - Operation ExportsOperations.list has a new parameter expand
  info	[Changelog]   - Removed operation group SettingsOperations

️❌ azure-resource-manager-schemas failed [Detail]

• ❌Failed [Logs] Generate from ce2010e7c85ca3608176c698f7350e03421d52e4. 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
  warn	No file changes detected after generation

• ❌cost-management/resource-manager [View full logs] 

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

• ️✔️Succeeded [Logs] Generate from ce2010e7c85ca3608176c698f7350e03421d52e4. 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.Cost [View full logs]  [Preview SDK Changes]
  • Az.Cost.0.1.0.nupkg

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

[openapi-workflow-bot]

Hi @GuillaumeColom, 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.

[openapi-workflow-bot]

NewApiVersionRequired reason:

A service’s API is a contract with customers and is represented by using the api-version query parameter. Changes such as adding an optional property to a request/response or introducing a new operation is a change to the service’s contract and therefore requires a new api-version value. This is critically important for documentation, client libraries, and customer support.

EXAMPLE: if a customer calls a service in the public cloud using api-version=2020-07-27, the new property or operation may exist but if they call the service in a government cloud, air-gapped cloud, or Azure Stack Hub cloud using the same api-version, the property or operation may not exist. Because there is no clear relationship between the service api-version and the new property/operation, customers can’t trust the documentation and Azure customer have difficulty helping customers diagnose issues. In addition, each client library version documents the service version it supports. When an optional property or new operation is added to a service and its Swagger, new client libraries must be produced to expose this functionality to customers. Without updating the api-version, it is unclear to customers which version of a client library supports these new features.

[openapi-workflow-bot]

Hi @GuillaumeColom, Your PR has some issues. Please fix the CI sequentially by following the order of Avocado, semantic validation, model validation, breaking change, lintDiff. If you have any questions, please post your questions in this channel https://aka.ms/swaggersupport.

Task	How to fix	Priority
Avocado	Fix-Avocado	High
Semantic validation	Fix-SemanticValidation-Error	High
Model validation	Fix-ModelValidation-Error	High
LintDiff	Fix-LintDiff	high

If you need further help, please feedback via swagger feedback.