Skip to content

Conversation

pjohari-ms
Copy link
Member

ARM (Control 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.

spec_pr_review_workflow_diagram

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

  • New resource provider.
  • New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
  • Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
  • Update existing version to fix OpenAPI spec quality issues in S360.
  • Other, please clarify:
    • edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

  • I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
  • I have reviewed following Resource Provider guidelines, including
    ARM resource provider contract and
    REST guidelines (estimated time: 4 hours).
    I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

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
suppressions guide to get approval.

Getting help

  • First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
  • 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.
  • For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
  • 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.

Copy link

openapi-pipeline-app bot commented May 2, 2024

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
    This PR has ARMChangesRequested label. Please address or respond to feedback from the ARM API reviewer.
    When you are ready to continue the ARM API review, please remove the ARMChangesRequested label.
    Automation should then add WaitForARMFeedback label.
    ❗If you don't have permissions to remove the label, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories.
    For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  • ❌ The required check named Automated merging requirements met has failed. This is the final check that must pass. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide. In addition, refer to step 4 in the PR workflow diagram

Copy link

openapi-pipeline-app bot commented May 2, 2024

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]
There are no breaking changes.
️❌Breaking Change(Cross-Version): 5 Errors, 0 Warnings failed [Detail]
Compared specs (v0.10.8) new version base version
cosmos-db.json 2024-05-15-preview(b2f9454) 2023-11-15(main)
cosmos-db.json 2024-05-15-preview(b2f9454) 2024-02-15-preview(main)

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

Rule Message
1023 - TypeFormatChanged The new version has a different format 'arm-id' than the previous one ''.
New: common-types/resource-management/v5/types.json#L14:9
Old: common-types/resource-management/v1/types.json#L14:9
1023 - TypeFormatChanged The new version has a different format 'arm-id' than the previous one ''.
New: common-types/resource-management/v5/types.json#L14:9
Old: common-types/resource-management/v1/types.json#L14:9
1023 - TypeFormatChanged The new version has a different format 'arm-id' than the previous one ''.
New: common-types/resource-management/v5/types.json#L14:9
Old: common-types/resource-management/v1/types.json#L14:9
1023 - TypeFormatChanged The new version has a different format 'arm-id' than the previous one ''.
New: common-types/resource-management/v5/types.json#L14:9
Old: common-types/resource-management/v1/types.json#L14:9
1023 - TypeFormatChanged The new version has a different format 'arm-id' than the previous one ''.
New: common-types/resource-management/v5/types.json#L14:9
Old: common-types/resource-management/v1/types.json#L14:9
️❌LintDiff: 4 Errors, 0 Warnings failed [Detail]
Compared specs (v2.2.2) new version base version
package-preview-2024-05 package-preview-2024-05(b2f9454) package-preview-2024-05(release-cosmos-db-Microsoft.DocumentDB-2024-05-15-preview)

[must fix]The following errors/warnings are introduced by current PR:

Rule Message Related RPC [For API reviewers]
NextLinkPropertyMustExist The property 'nextLink' specified by nextLinkName does not exist in the 200 response schema. Please, specify the name of the property that provides the nextLink. If the model does not have the nextLink property then specify null.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L254
RPC-Get-V1-06
XmsPageableMustHaveCorrespondingResponse The operation: 'DatabaseAccounts_List' is defined with x-ms-pageable enabled,but can not find the corresponding nextLink property in the response, please add it.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L254
NextLinkPropertyMustExist The property 'nextLink' specified by nextLinkName does not exist in the 200 response schema. Please, specify the name of the property that provides the nextLink. If the model does not have the nextLink property then specify null.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L284
RPC-Get-V1-06
XmsPageableMustHaveCorrespondingResponse The operation: 'DatabaseAccounts_ListByResourceGroup' is defined with x-ms-pageable enabled,but can not find the corresponding nextLink property in the response, please add it.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L284


The following errors/warnings exist before current PR submission:

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

Rule Message
GetCollectionResponseSchema The response in the GET collection operation 'CassandraClusters_ListCommand' does not match the response definition in the individual GET operation 'CassandraClusters_GetCommandAsync' .
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L36
PatchResponseCodes Long-running PATCH operations must have responses with 200, 202 and default return codes. They also must not have other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L69
PatchBodyParametersSchema Properties of a PATCH request body must not be required, property:defaultConsistencyLevel.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L95
PatchBodyParametersSchema Properties of a PATCH request body must not be required, property:type.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L95
PutResponseCodes Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L110
DeleteResponseCodes Long-running delete operations must have responses with 202, 204 and default return codes. They also must have no other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L157
PostResponseCodes Long-running POST operations must have responses with 202 and default return codes. They must also have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified. They also must not have other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L201
PostResponseCodes Synchronous POST operations must have one of the following combinations of responses - 200 and default ; 204 and default. They also must not have other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L317
PostResponseCodes Synchronous POST operations must have one of the following combinations of responses - 200 and default ; 204 and default. They also must not have other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L350
PostResponseCodes 200 return code does not have a schema specified. LRO POST must have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L386
DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L435
PostResponseCodes 200 return code does not have a schema specified. LRO POST must have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L445
DefaultErrorResponseSchema the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L494
XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L504
PostResponseCodes Synchronous POST operations must have one of the following combinations of responses - 200 and default ; 204 and default. They also must not have other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L535
PostResponseCodes Long-running POST operations must have responses with 202 and default return codes. They must also have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified. They also must not have other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L568
NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L641
OperationsApiResponseSchema The response schema of operations API '/providers/Microsoft.DocumentDB/operations' does not match the ARM specification. Please standardize the schema.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L667
OperationsApiSchemaUsesCommonTypes Operations API path must follow the schema provided in the common types.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L668
PathForNestedResource The path for nested resource doest not meet the valid resource pattern. There is one exception for extension resources with fully qualified path and the author can go ahead and suppress the error(look at https://github.com/Azure/azure-openapi-validator/blob/main/docs/path-for-nested-resource.md#pathfornestedresource for more details)
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L938
PathForNestedResource The path for nested resource doest not meet the valid resource pattern. There is one exception for extension resources with fully qualified path and the author can go ahead and suppress the error(look at https://github.com/Azure/azure-openapi-validator/blob/main/docs/path-for-nested-resource.md#pathfornestedresource for more details)
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L980
PutResponseCodes Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L1570
DeleteResponseCodes Long-running delete operations must have responses with 202, 204 and default return codes. They also must have no other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L1627
PutResponseCodes Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L1747
DeleteResponseCodes Long-running delete operations must have responses with 202, 204 and default return codes. They also must have no other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L1807
EvenSegmentedPathForPutOperation API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments).
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L1853
XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L1854
PutResponseCodes Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L1888
PutResponseCodes Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L2135
PutResponseCodes Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes.
Location: Microsoft.DocumentDB/preview/2024-05-15-preview/cosmos-db.json#L2273
️️✔️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.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️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?

Copy link

openapi-pipeline-app bot commented May 2, 2024

Swagger Generation Artifacts

️️✔️ApiDocPreview succeeded [Detail] [Expand]
 Please click here to preview with your @microsoft account. 
️❌ azure-sdk-for-python failed [Detail]
  • Code Generator Failed in generating from 479d4608af346eb5e1793a3ee8b6566b740bc8b4. 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.
    cmderr	[automation_init.sh]
    cmderr	[automation_init.sh] npm notice New minor version of npm available! 10.5.0 -> 10.7.0
    cmderr	[automation_init.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.7.0>
    cmderr	[automation_init.sh] npm notice Run `npm install -g [email protected]` to update!
    cmderr	[automation_init.sh] npm notice
    command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/autorest/codegen/templates/operationgroup.py.jinja2", line 74, in top-level template code
    cmdout	[automation_generate.sh] [Autorest]     {{ someop()|indent }}
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/venv/lib/python3.10/site-packages/jinja2/runtime.py", line 777, in invoke
    cmdout	[automation_generate.sh] [Autorest]     rv = self._func(*arguments)
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/autorest/codegen/templates/operationgroup.py.jinja2", line 70, in template
    cmdout	[automation_generate.sh] [Autorest]     {% macro someop() %}{% include "paging_operation.py.jinja2" %}{% endmacro %}
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/autorest/codegen/templates/pagingoperation.py.jinja2", line 16, in top-level template code
    cmdout	[automation_generate.sh] [Autorest]     {{ optools.serialize(operation_serializer.set_up_params_forpager(operation)) | indent }}
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/autorest/codegen/serializers/builder_serializer.py", line 1543, in set_up_params_forpager
    cmdout	[automation_generate.sh] [Autorest]     retval.extend(self.extract_datacallback(builder))
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/autorest/codegen/serializers/builder_serializer.py", line 1513, in _extract_datacallback
    cmdout	[automation_generate.sh] [Autorest]     continuationtoken_name = builder.continuation_tokenname
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/autorest/codegen/models/paging_operation.py", line 101, in continuation_tokenname
    cmdout	[automation_generate.sh] [Autorest]     return self.get_attr_name(wirename)
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/autorest/codegen/models/paging_operation.py", line 87, in _get_attrname
    cmdout	[automation_generate.sh] [Autorest]     raise ValueError(
    cmdout	[automation_generate.sh] [Autorest] ValueError: Can't find a matching property in response for nextLink
    cmdout	[automation_generate.sh] [Autorest] fatal   | Process() cancelled due to failure
    cmdout	[automation_generate.sh] [Autorest] error   |   Error: Plugin codegen reported failure.
    cmdout	[automation_generate.sh] [Autorest] error   | Autorest completed with an error. If you think the error message is unclear, or is a bug, please declare an issues at https://github.com/Azure/autorest/issues with the error message you are seeing.
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/autorest/codegen/templates/operationgroup.py.jinja2", line 74, in top-level template code
    cmdout	[automation_generate.sh] [Autorest]     {{ someop()|indent }}
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/venv/lib/python3.10/site-packages/jinja2/runtime.py", line 777, in invoke
    cmdout	[automation_generate.sh] [Autorest]     rv = self._func(*arguments)
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/autorest/codegen/templates/operationgroup.py.jinja2", line 70, in template
    cmdout	[automation_generate.sh] [Autorest]     {% macro someop() %}{% include "paging_operation.py.jinja2" %}{% endmacro %}
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/autorest/codegen/templates/pagingoperation.py.jinja2", line 16, in top-level template code
    cmdout	[automation_generate.sh] [Autorest]     {{ optools.serialize(operation_serializer.set_up_params_forpager(operation)) | indent }}
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/autorest/codegen/serializers/builder_serializer.py", line 1543, in set_up_params_forpager
    cmdout	[automation_generate.sh] [Autorest]     retval.extend(self.extract_datacallback(builder))
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/autorest/codegen/serializers/builder_serializer.py", line 1513, in _extract_datacallback
    cmdout	[automation_generate.sh] [Autorest]     continuationtoken_name = builder.continuation_tokenname
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/autorest/codegen/models/paging_operation.py", line 101, in continuation_tokenname
    cmdout	[automation_generate.sh] [Autorest]     return self.get_attr_name(wirename)
    cmdout	[automation_generate.sh] [Autorest]   File "/home/cloudtest/.autorest/@[email protected]/node_modules/@autorest/python/autorest/codegen/models/paging_operation.py", line 87, in _get_attrname
    cmdout	[automation_generate.sh] [Autorest]     raise ValueError(
    cmdout	[automation_generate.sh] [Autorest] ValueError: Can't find a matching property in response for nextLink
    cmdout	[automation_generate.sh] [Autorest] fatal   | Process() cancelled due to failure
    cmdout	[automation_generate.sh] [Autorest] error   |   Error: Plugin codegen reported failure.
    cmdout	[automation_generate.sh] [Autorest] error   | Autorest completed with an error. If you think the error message is unclear, or is a bug, please declare an issues at https://github.com/Azure/autorest/issues with the error message you are seeing.
    cmdout	[automation_generate.sh] [Autorest]/mnt/vss/_work/1/s/azure-sdk-for-python_tmp/venv-sdk/auto_temp.json does not exist!!!Error happened during codegen
    error	Script return with result [failed] code [1] signal [null] cwd [azure-sdk-for-python]: sh scripts/automation_generate.sh
    warn	Skip package processing as generation is failed
️️✔️ azure-sdk-for-net-track2 succeeded [Detail] [Expand]
  • ️✔️Succeeded in generating from 479d4608af346eb5e1793a3ee8b6566b740bc8b4. 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
    command	pwsh ./eng/scripts/Invoke-GenerateAndBuildV2.ps1 ../azure-sdk-for-net_tmp/generateInput.json ../azure-sdk-for-net_tmp/generateOutput.json
  • ️✔️Azure.ResourceManager.CosmosDB [Preview SDK Changes]
    • Azure.ResourceManager.CosmosDB.1.4.0-alpha.20240503.1.nupkg
    info	[Changelog]
️❌ azure-sdk-for-java failed [Detail]
  • Pipeline Framework Failed in generating from 479d4608af346eb5e1793a3ee8b6566b740bc8b4. 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
    command	./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json
    cmderr	[generate.py] [COMPILE] Maven build fail.
    cmderr	[generate.py] You can inquire in "Language - Java" Teams channel. Please include the link of this Pull Request in the query.
    To https://github.com/azure-sdk/azure-sdk-for-java!	refs/heads/main:refs/heads/main	[remote rejected] (protected branch hook declined)DonePushing to https://github.com/azure-sdk/azure-sdk-for-javaPOST git-receive-pack (720743 bytes)remote: error: GH006: Protected branch update failed for refs/heads/main.        remote: error: Cannot force-push to this branch        error: failed to push some refs to 'https://github.com/azure-sdk/azure-sdk-for-java'
  • ️✔️azure-resourcemanager-cosmos-generated
    error	Fatal error: To https://github.com/azure-sdk/azure-sdk-for-java!	refs/heads/main:refs/heads/main	[remote rejected] (protected branch hook declined)DonePushing to https://github.com/azure-sdk/azure-sdk-for-javaPOST git-receive-pack (720743 bytes)remote: error: GH006: Protected branch update failed for refs/heads/main.        remote: error: Cannot force-push to this branch        error: failed to push some refs to 'https://github.com/azure-sdk/azure-sdk-for-java'
    error	Fatal error: Error: To https://github.com/azure-sdk/azure-sdk-for-java!	refs/heads/main:refs/heads/main	[remote rejected] (protected branch hook declined)DonePushing to https://github.com/azure-sdk/azure-sdk-for-javaPOST git-receive-pack (720743 bytes)remote: error: GH006: Protected branch update failed for refs/heads/main.        remote: error: Cannot force-push to this branch        error: failed to push some refs to 'https://github.com/azure-sdk/azure-sdk-for-java'    at Object.action (/mnt/vss/_work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/[email protected]/node_modules/simple-git/dist/cjs/index.js:1332:25)    at PluginStore.exec (/mnt/vss/_work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/[email protected]/node_modules/simple-git/dist/cjs/index.js:1367:29)    at /mnt/vss/_work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/[email protected]/node_modules/simple-git/dist/cjs/index.js:1766:43    at new Promise (<anonymous>)    at GitExecutorChain.handleTaskData (/mnt/vss/_work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/[email protected]/node_modules/simple-git/dist/cjs/index.js:1764:16)    at GitExecutorChain.<anonymous> (/mnt/vss/_work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/[email protected]/node_modules/simple-git/dist/cjs/index.js:1748:44)    at Generator.next (<anonymous>)    at fulfilled (/mnt/vss/_work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/[email protected]/node_modules/simple-git/dist/cjs/index.js:55:24)    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    error	The following packages are still pending:
    error		azure-resourcemanager-cosmos-generated
️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
  • ️✔️Succeeded in generating from 479d4608af346eb5e1793a3ee8b6566b740bc8b4. 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/cosmos/armcosmos [Preview SDK Changes]
️🔄 azure-sdk-for-js inProgress [Detail]
️❌ azure-resource-manager-schemas failed [Detail]
  • Failed in generating from 479d4608af346eb5e1793a3ee8b6566b740bc8b4. 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] npm notice
    cmderr	[initScript.sh] npm notice New minor version of npm available! 10.5.0 -> 10.7.0
    cmderr	[initScript.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.7.0>
    cmderr	[initScript.sh] npm notice Run `npm install -g [email protected]` to update!
    cmderr	[initScript.sh] npm notice
    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
  • cosmos-db/resource-manager [Preview Schema Changes]
️⚠️ azure-powershell warning [Detail]
  • ⚠️Warning in generating from 479d4608af346eb5e1793a3ee8b6566b740bc8b4. 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.cosmos-db.DefaultTag [Preview SDK Changes]
Posted by Swagger Pipeline | How to fix these errors?

Copy link

openapi-pipeline-app bot commented May 2, 2024

@AzureRestAPISpecReview AzureRestAPISpecReview added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label May 3, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added no-recent-activity There has been no recent activity on this issue. and removed no-recent-activity There has been no recent activity on this issue. labels May 20, 2024
@razvanbadea-msft
Copy link
Member

Please fill out the Purpose of this PR and Due diligence checklist

@razvanbadea-msft
Copy link
Member

Fix the Swagger LintDiff errors about missing nextLink property

@razvanbadea-msft razvanbadea-msft added the ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review label May 22, 2024
@openapi-pipeline-app openapi-pipeline-app bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label May 22, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added no-recent-activity There has been no recent activity on this issue. and removed no-recent-activity There has been no recent activity on this issue. labels Jun 10, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added no-recent-activity There has been no recent activity on this issue. and removed no-recent-activity There has been no recent activity on this issue. labels Jun 24, 2024
Copy link
Contributor

Hi, @pjohari-ms. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity label.

@microsoft-github-policy-service microsoft-github-policy-service bot added the no-recent-activity There has been no recent activity on this issue. label Jul 15, 2024
Copy link
Contributor

Hi, @pjohari-ms. The PR will be closed since the PR has no update for 28 days. If you still need the PR review to proceed, please reopen it and @ mention PR assignee.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review ARMReview no-recent-activity There has been no recent activity on this issue. resource-manager
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants