[Batch] Switch contentLength from int64 to string

[dpwatrous]

This is a breaking change, but accurately reflects what the Batch service has always returned for this property.

Data Plane API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

API Info: The Basics

Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

• Link to API Spec engagement record issue:

Is this review for (select one):

• a private preview
• a public preview
• GA release

Change Scope

^{This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.}

• Design Document:
• Previous API Spec Doc:
• Updated paths:

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.

❔Got questions? Need additional info?? We are here to help!

Contact us!

The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

• 💬 Teams Channel
• 💌 email

Click here for links to tools, specs, guidelines & other good stuff

Tooling

• Open API validation tools were run on this PR. Go here to see how to fix errors
• Spectral Linting

Guidelines & Specifications

• Azure REST API Guidelines
• OpenAPI Style Guidelines
• Azure Breaking Change Policy

Helpful Links

• Schedule a data plane REST API spec review

Getting help

• First, please carefully read through this PR description, from top to bottom.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
  and https://aka.ms/ci-fix.
• If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
  This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

[openapi-pipeline-app]

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

[openapi-pipeline-app]

Swagger Validation Report

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

Compared specs (v0.10.12)	new version	base version
BatchService.json	2024-02-01.19.0(d994bc4)	2024-02-01.19.0(main)

Rule	Message
❌ 1023 - TypeFormatChanged	The new version has a different format '' than the previous one 'int64'. New: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L14264:9 Old: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L14268:9
❌ 1023 - TypeFormatChanged	The new version has a different format '' than the previous one 'int64'. New: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L2493:15 Old: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L2493:15
❌ 1023 - TypeFormatChanged	The new version has a different format '' than the previous one 'int64'. New: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L2731:15 Old: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L2732:15
❌ 1023 - TypeFormatChanged	The new version has a different format '' than the previous one 'int64'. New: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L6847:15 Old: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L6849:15
❌ 1023 - TypeFormatChanged	The new version has a different format '' than the previous one 'int64'. New: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L7085:15 Old: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L7088:15
❌ 1026 - TypeChanged	The new version has a different type 'string' than the previous one 'integer'. New: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L14264:9 Old: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L14268:9
❌ 1026 - TypeChanged	The new version has a different type 'string' than the previous one 'integer'. New: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L2493:15 Old: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L2493:15
❌ 1026 - TypeChanged	The new version has a different type 'string' than the previous one 'integer'. New: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L2731:15 Old: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L2732:15
❌ 1026 - TypeChanged	The new version has a different type 'string' than the previous one 'integer'. New: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L6847:15 Old: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L6849:15
❌ 1026 - TypeChanged	The new version has a different type 'string' than the previous one 'integer'. New: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L7085:15 Old: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L7088:15

️️✔️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 specs (v2.2.2)	new version	base version
package-2024-02.19.0-preview	package-2024-02.19.0-preview(d994bc4)	package-2024-02.19.0-preview(main)

The following errors/warnings exist before current PR submission:

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

Rule	Message
❌ LroExtension	Operations with a 202 response must specify x-ms-long-running-operation: true. GET operation is excluded from the validation as GET will have 202 only if it is a polling action & hence x-ms-long-running-operation wouldn't be defined Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L895
❌ LroExtension	Operations with a 202 response must specify x-ms-long-running-operation: true. GET operation is excluded from the validation as GET will have 202 only if it is a polling action & hence x-ms-long-running-operation wouldn't be defined Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L1116
❌ LroExtension	Operations with a 202 response must specify x-ms-long-running-operation: true. GET operation is excluded from the validation as GET will have 202 only if it is a polling action & hence x-ms-long-running-operation wouldn't be defined Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L1255
❌ LroExtension	Operations with a 202 response must specify x-ms-long-running-operation: true. GET operation is excluded from the validation as GET will have 202 only if it is a polling action & hence x-ms-long-running-operation wouldn't be defined Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L3167
❌ LroExtension	Operations with a 202 response must specify x-ms-long-running-operation: true. GET operation is excluded from the validation as GET will have 202 only if it is a polling action & hence x-ms-long-running-operation wouldn't be defined Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L3952
❌ LroExtension	Operations with a 202 response must specify x-ms-long-running-operation: true. GET operation is excluded from the validation as GET will have 202 only if it is a polling action & hence x-ms-long-running-operation wouldn't be defined Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L4579
❌ LroExtension	Operations with a 202 response must specify x-ms-long-running-operation: true. GET operation is excluded from the validation as GET will have 202 only if it is a polling action & hence x-ms-long-running-operation wouldn't be defined Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L5356
❌ LroExtension	Operations with a 202 response must specify x-ms-long-running-operation: true. GET operation is excluded from the validation as GET will have 202 only if it is a polling action & hence x-ms-long-running-operation wouldn't be defined Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L7140
❌ LroExtension	Operations with a 202 response must specify x-ms-long-running-operation: true. GET operation is excluded from the validation as GET will have 202 only if it is a polling action & hence x-ms-long-running-operation wouldn't be defined Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L7785
❌ LroExtension	Operations with a 202 response must specify x-ms-long-running-operation: true. GET operation is excluded from the validation as GET will have 202 only if it is a polling action & hence x-ms-long-running-operation wouldn't be defined Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L7924
❌ LroExtension	Operations with a 202 response must specify x-ms-long-running-operation: true. GET operation is excluded from the validation as GET will have 202 only if it is a polling action & hence x-ms-long-running-operation wouldn't be defined Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L8063
⚠️ VersionConvention	API version should be a date in YYYY-MM-DD format, optionally suffixed with '-preview'. Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L5
⚠️ SecurityDefinitionDescription	Security definition should have a description. Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L45
⚠️ 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: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L82
⚠️ PaginationResponse	value property in pageable response should be required Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L115
⚠️ ErrorResponse	Error response should contain a x-ms-error-code header. Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L138
⚠️ ErrorResponse	Error response schema should contain an object property named error. Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L140
⚠️ PageableOperation	Based on the response model schema, operation 'Batch_GetApplication' might be pageable. Consider adding the x-ms-pageable extension. Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L156
⚠️ PaginationResponse	Operation might be pageable. Consider adding the x-ms-pageable extension. Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L156
⚠️ 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: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L181
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L199
⚠️ ErrorResponse	Error response should contain a x-ms-error-code header. Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L233
⚠️ ErrorResponse	Error response schema should contain an object property named error. Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L235
⚠️ SummaryAndDescriptionMustNotBeSame	The summary and description values should not be same. Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L248
⚠️ 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: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L273
⚠️ ParameterNamesConvention	Parameter name '$filter' should not begin with '$' or '@'. Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L303
⚠️ ParameterNamesConvention	Parameter name '$select' should not begin with '$' or '@'. Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L310
⚠️ ParameterNamesConvention	Parameter name '$expand' should not begin with '$' or '@'. Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L321
⚠️ PaginationResponse	value property in pageable response should be required Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L335
⚠️ ErrorResponse	Error response should contain a x-ms-error-code header. Location: Azure.Batch/preview/2024-02-01.19.0/BatchService.json#L358

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

Validation passes for Avocado.

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

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

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

Validation passes for SpellCheck.

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

Validation passes for Lint(RPaaS).

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

Validation passes for Summary.

️️✔️Automated merging requirements met succeeded [Detail] [Expand]

_{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. 

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

For more instructions, please refer to the FAQ .
• ⚠️Warning in generating from 8942c8ef8a0721c1c87ca1221766c8f873b2bbb5. SDK Automation 14.0.0

  command	pwsh ./eng/scripts/Automation-Sdk-Init.ps1 ../azure-sdk-for-net_tmp/initInput.json ../azure-sdk-for-net_tmp/initOutput.json
  warn		Warning: azure-sdk-for-net-track2 cannot be found in specification/batch/data-plane/readme.md. This SDK will be skipped from SDK generation. Please add the right config to the readme file according to this guidance https://github.com/Azure/azure-rest-api-specs/blob/main/documentation/code-gen/configure-go-sdk.md#swagger-to-sdk.
  command	pwsh ./eng/scripts/Invoke-GenerateAndBuildV2.ps1 ../azure-sdk-for-net_tmp/generateInput.json ../azure-sdk-for-net_tmp/generateOutput.json
  cmderr	[Invoke-GenerateAndBuildV2.ps1] npm notice
  cmderr	[Invoke-GenerateAndBuildV2.ps1] npm notice New minor version of npm available! 10.7.0 -> 10.8.2
  cmderr	[Invoke-GenerateAndBuildV2.ps1] npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.2
  cmderr	[Invoke-GenerateAndBuildV2.ps1] npm notice To update run: npm install -g [email protected]
  cmderr	[Invoke-GenerateAndBuildV2.ps1] npm notice
  cmderr	[Invoke-GenerateAndBuildV2.ps1] Get-ChildItem: /mnt/vss/_work/1/s/azure-sdk-for-net/eng/scripts/automation/GenerateAndBuildLib.ps1:787
  cmderr	[Invoke-GenerateAndBuildV2.ps1] Line |
  cmderr	[Invoke-GenerateAndBuildV2.ps1]  787 |  … rtifacts += Get-ChildItem $artifactsPath -Filter *.nupkg -exclude *.s …
  cmderr	[Invoke-GenerateAndBuildV2.ps1]      |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  cmderr	[Invoke-GenerateAndBuildV2.ps1]      | Cannot find path
  cmderr	[Invoke-GenerateAndBuildV2.ps1]      | '/mnt/vss/_work/1/s/azure-sdk-for-net/artifacts/packages/Debug/' because
  cmderr	[Invoke-GenerateAndBuildV2.ps1]      | it does not exist.
  cmderr	[Invoke-GenerateAndBuildV2.ps1] GeneratePackage: /mnt/vss/_work/1/s/azure-sdk-for-net/eng/scripts/Invoke-GenerateAndBuildV2.ps1:144
  cmderr	[Invoke-GenerateAndBuildV2.ps1] Line |
  cmderr	[Invoke-GenerateAndBuildV2.ps1]  144 |              GeneratePackage `
  cmderr	[Invoke-GenerateAndBuildV2.ps1]      |              ~~~~~~~~~~~~~~~~~
  cmderr	[Invoke-GenerateAndBuildV2.ps1]      | Failed to generate sdk artifact

• ️✔️Azure.Batch [Preview SDK Changes]

  info	[Changelog]

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

For more instructions, please refer to the FAQ .
• ❌Failed in generating from 8942c8ef8a0721c1c87ca1221766c8f873b2bbb5. SDK Automation 14.0.0

  command	./eng/automation/init.sh ../azure-sdk-for-java_tmp/initInput.json ../azure-sdk-for-java_tmp/initOutput.json
  warn		Warning: azure-sdk-for-java cannot be found in specification/batch/data-plane/readme.md. This SDK will be skipped from SDK generation. Please add the right config to the readme file according to this guidance https://github.com/Azure/azure-rest-api-specs/blob/main/documentation/code-gen/configure-go-sdk.md#swagger-to-sdk.
  command	./eng/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json
  command	./eng/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json
  cmderr	[Java-Sdk-Automation] [COMPILE] Maven build fail.
  cmderr	[Java-Sdk-Automation] [COMPILE] Maven build fail.
  info	[Changelog]
  command	./eng/automation/install_instruction.py ../azure-sdk-for-java_tmp/installInstructionInput.json ../azure-sdk-for-java_tmp/installInstructionOutput.json

• ❌azure-compute-batch [Preview SDK Changes]

  info	[Changelog]

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

For more instructions, please refer to the FAQ .
• ⚠️Warning in generating from 8942c8ef8a0721c1c87ca1221766c8f873b2bbb5. 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] W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
  cmderr	[automation_init.sh] W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
  cmderr	[automation_init.sh] W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
  cmderr	[automation_init.sh] W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
  cmderr	[automation_init.sh] W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
  cmderr	[automation_init.sh] W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
  cmderr	[automation_init.sh] W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
  cmderr	[automation_init.sh] W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
  cmderr	[automation_init.sh] W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
  cmderr	[automation_init.sh] W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
  cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
  cmderr	[automation_init.sh] npm notice
  cmderr	[automation_init.sh] npm notice New minor version of npm available! 10.7.0 -> 10.8.2
  cmderr	[automation_init.sh] npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.2
  cmderr	[automation_init.sh] npm notice To update run: npm install -g [email protected]
  cmderr	[automation_init.sh] npm notice
  warn		Warning: azure-sdk-for-python cannot be found in specification/batch/data-plane/readme.md. This SDK will be skipped from SDK generation. Please add the right config to the readme file according to this guidance https://github.com/Azure/azure-rest-api-specs/blob/main/documentation/code-gen/configure-go-sdk.md#swagger-to-sdk.
  command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json

• ️✔️azure-batch [Preview SDK Changes]

  info	[Changelog] data-plan skip changelog generation temporarily

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

For more instructions, please refer to the FAQ .
• ❌Failed in generating from 8942c8ef8a0721c1c87ca1221766c8f873b2bbb5. 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	Warning: File azure-sdk-for-js_tmp/initOutput.json not found to read. Please re-run the pipeline if the error is transitient error or report this issue through https://aka.ms/azsdk/support/specreview-channel.
  warn		Warning: azure-sdk-for-js cannot be found in specification/batch/data-plane/readme.md. This SDK will be skipped from SDK generation. Please add the right config to the readme file according to this guidance https://github.com/Azure/azure-rest-api-specs/blob/main/documentation/code-gen/configure-go-sdk.md#swagger-to-sdk.
  command	sh .scripts/automation_generate.sh ../azure-sdk-for-js_tmp/generateInput.json ../azure-sdk-for-js_tmp/generateOutput.json
  command	sh .scripts/automation_generate.sh ../azure-sdk-for-js_tmp/generateInput.json ../azure-sdk-for-js_tmp/generateOutput.json
  cmderr	[automation_generate.sh] [ERROR] Error:
  cmderr	[automation_generate.sh] [ERROR] Error:
  cmderr	[automation_generate.sh] [ERROR] An error occurred while run build for typespec project: "specification/batch/Azure.Batch":
  cmderr	[automation_generate.sh] [ERROR] An error occurred while run build for typespec project: "specification/batch/Azure.Batch":
  cmderr	[automation_generate.sh] [ERROR] Err: Error: Command failed: rush build -t @azure-rest/batch
  cmderr	[automation_generate.sh] [ERROR] Err: Error: Command failed: rush build -t @azure-rest/batch
  cmderr	[automation_generate.sh] [ERROR] Stderr: "null"
  cmderr	[automation_generate.sh] [ERROR] Stderr: "null"
  cmderr	[automation_generate.sh] [ERROR] Stdout: "null"
  cmderr	[automation_generate.sh] [ERROR] Stdout: "null"
  cmderr	[automation_generate.sh] [ERROR] ErrorStack: "Error: Command failed: rush build -t @azure-rest/batch
  cmderr	[automation_generate.sh] [ERROR] ErrorStack: "Error: Command failed: rush build -t @azure-rest/batch
  cmderr	[automation_generate.sh] [ERROR]     at checkExecSyncError (node:child_process:885:11)
  cmderr	[automation_generate.sh] [ERROR]     at checkExecSyncError (node:child_process:885:11)
  cmderr	[automation_generate.sh] [ERROR]     at execSync (node:child_process:957:15)
  cmderr	[automation_generate.sh] [ERROR]     at execSync (node:child_process:957:15)
  cmderr	[automation_generate.sh] [ERROR]     at /home/cloudtest/.nvm/versions/node/v18.15.0/lib/node_modules/@azure-tools/js-sdk-release-tools/dist/llc/generateRLCInPipeline/generateRLCInPipeline.js:209:42
  cmderr	[automation_generate.sh] [ERROR]     at /home/cloudtest/.nvm/versions/node/v18.15.0/lib/node_modules/@azure-tools/js-sdk-release-tools/dist/llc/generateRLCInPipeline/generateRLCInPipeline.js:209:42
  cmderr	[automation_generate.sh] [ERROR]     at Generator.next (<anonymous>)
  cmderr	[automation_generate.sh] [ERROR]     at Generator.next (<anonymous>)
  cmderr	[automation_generate.sh] [ERROR]     at fulfilled (/home/cloudtest/.nvm/versions/node/v18.15.0/lib/node_modules/@azure-tools/js-sdk-release-tools/node_modules/tslib/tslib.js:112:62)
  cmderr	[automation_generate.sh] [ERROR]     at fulfilled (/home/cloudtest/.nvm/versions/node/v18.15.0/lib/node_modules/@azure-tools/js-sdk-release-tools/node_modules/tslib/tslib.js:112:62)
  cmderr	[automation_generate.sh] [ERROR]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"
  cmderr	[automation_generate.sh] [ERROR]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"
  info	[Changelog]
  error	breakingChangeTracking is enabled, but version or changelogItem is not found in output.

• ❌@azure-rest/batch [Preview SDK Changes]

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

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

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
Python	azure-batch	https://apiview.dev/Assemblies/Review/f55ec97aa8334043977fd119ec8b5c02?revisionId=37dd4aa48c134ccb94e71584ccb49303
Swagger	Azure.Batch	https://apiview.dev/Assemblies/Review/57d5469e8d87431b9a2e2c42788db46d?revisionId=8b87bbb11d46489aad6ccbcd2c9bb4ee
TypeSpec	Azure.Batch	https://apiview.dev/Assemblies/Review/d63619c650994f368464a4bff0c61f13?revisionId=f400f6f034804c5f9a8d6f08afe72653

[wiboris]

changes look good

[dpwatrous]

Note that this TypeSpec is currently in a preview state. This change was made after discussing options to represent the current service behavior in the breaking change office hour.

[raych1]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[dpwatrous]

@raych1 is there anything blocking this from being merged? I'm not sure what the VersionReviewRequired tag is, but if it's regarding making changes to an existing API version, I think we should be fine. The TypeSpec in this PR is in a public preview state, not GA.

[dpwatrous]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[dpwatrous]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).