Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding base commit for new API Preview Version 2023-07-31-preview #26900

Conversation

RamyaElangovanP
Copy link
Contributor

@RamyaElangovanP RamyaElangovanP commented Nov 30, 2023

ARM (Control Plane) API Specification Update Pull Request

PR review workflow diagram

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

diagram

Click here to see the details of Step 1

Breaking changes review (Diagram Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

  • The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
  • You believe there is no need for you to request breaking change approval, for any reason.
    Such claims must be reviewed, and the process is the same.
Click here to see the details of Step 2

ARM API changes review (Diagram Step 2)

  • If this PR is in purview of ARM review then automation will add the ARMReview label.
  • If you want to force ARM review, add the label yourself.
  • Proceed according to the diagram at the top of this comment.
Click here to see the diagram footnotes

Diagram footnotes

[1] ARM review queue (for merge queues, see [2])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])

If you need further help with anything, see Getting help section below.

Purpose of this PR

What's the purpose of this PR? Check all that apply. This is mandatory!

  • New API version. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
  • 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 swagger 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
Swagger-Suppression-Process
to get approval.

Getting help

  • For general PR approval workflow, see the diagram at the top of this comment.
  • 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.

Copy link

openapi-pipeline-app bot commented Nov 30, 2023

Next Steps to Merge

✔️ All automated merging requirements have been met! Refer to step 4 in the PR workflow diagram (even if your PR is for data plane, not ARM).

Copy link

openapi-pipeline-app bot commented Nov 30, 2023

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]
There are no breaking changes.
️⚠️Breaking Change(Cross-Version): 16 Warnings warning [Detail]
compared swaggers (via Oad v0.10.4)] new version base version
ManagedIdentity.json 2023-07-31-preview(da815d9) 2023-01-31(main)
ManagedIdentity.json 2023-07-31-preview(da815d9) 2022-01-31-preview(main)

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

Rule Message
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{resourceName}/listAssociatedResources' removed or restructured?
Old: Microsoft.ManagedIdentity/preview/2022-01-31-preview/ManagedIdentity.json#L178:5
⚠️ 1007 - RemovedClientParameter The new version is missing a client parameter that was found in the old version. Was 'FilterParameter' removed or renamed?
New: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L905:3
Old: Microsoft.ManagedIdentity/preview/2022-01-31-preview/ManagedIdentity.json#L978:3
⚠️ 1007 - RemovedClientParameter The new version is missing a client parameter that was found in the old version. Was 'OrderbyParameter' removed or renamed?
New: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L905:3
Old: Microsoft.ManagedIdentity/preview/2022-01-31-preview/ManagedIdentity.json#L978:3
⚠️ 1007 - RemovedClientParameter The new version is missing a client parameter that was found in the old version. Was 'SkipQueryParameter' removed or renamed?
New: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L905:3
Old: Microsoft.ManagedIdentity/preview/2022-01-31-preview/ManagedIdentity.json#L978:3
⚠️ 1023 - TypeFormatChanged The new version has a different format than the previous one.
New: common-types/resource-management/v4/types.json#L14:9
Old: common-types/resource-management/v1/types.json#L14:9
⚠️ 1023 - TypeFormatChanged The new version has a different format than the previous one.
New: common-types/resource-management/v4/types.json#L14:9
Old: common-types/resource-management/v1/types.json#L14:9
⚠️ 1023 - TypeFormatChanged The new version has a different format than the previous one.
New: common-types/resource-management/v4/types.json#L14:9
Old: common-types/resource-management/v1/types.json#L14:9
⚠️ 1023 - TypeFormatChanged The new version has a different format than the previous one.
New: common-types/resource-management/v4/types.json#L14:9
Old: common-types/resource-management/v1/types.json#L14:9
⚠️ 1023 - TypeFormatChanged The new version has a different format than the previous one.
New: common-types/resource-management/v4/types.json#L14:9
Old: common-types/resource-management/v1/types.json#L14:9
⚠️ 1023 - TypeFormatChanged The new version has a different format than the previous one.
New: common-types/resource-management/v4/types.json#L14:9
Old: common-types/resource-management/v1/types.json#L14:9
⚠️ 1023 - TypeFormatChanged The new version has a different format than the previous one.
New: common-types/resource-management/v4/types.json#L14:9
Old: common-types/resource-management/v1/types.json#L14:9
⚠️ 1023 - TypeFormatChanged The new version has a different format than the previous one.
New: common-types/resource-management/v4/types.json#L14:9
Old: common-types/resource-management/v1/types.json#L14:9
⚠️ 1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
New: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L445:9
Old: Microsoft.ManagedIdentity/preview/2022-01-31-preview/ManagedIdentity.json#L466:9
⚠️ 1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
New: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L500:9
Old: Microsoft.ManagedIdentity/preview/2022-01-31-preview/ManagedIdentity.json#L521:9
⚠️ 1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
New: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L540:9
Old: Microsoft.ManagedIdentity/preview/2022-01-31-preview/ManagedIdentity.json#L561:9
⚠️ 1036 - ConstraintChanged The new version has a different 'pattern' value than the previous one.
New: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L962:5
Old: Microsoft.ManagedIdentity/preview/2022-01-31-preview/ManagedIdentity.json#L1061:5
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 4 Warnings warning [Detail]
compared tags (via openapi-validator v2.1.6) new version base version
package-2023-07-31-preview package-2023-07-31-preview(da815d9) default(main)

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

Rule Message Related RPC [For API reviewers]
⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'scope'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L361
⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L361
⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'resourceGroupName'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L361
⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L361


The following errors/warnings exist before current PR submission:

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

Rule Message
OperationsApiResponseSchema The response schema of operations API '/providers/Microsoft.ManagedIdentity/operations' does not match the ARM specification. Please standardize the schema.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L87
OperationsApiSchemaUsesCommonTypes Operations API path must follow the schema provided in the common types.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L88
ResourceNameRestriction The resource name parameter 'resourceName' should be defined with a 'pattern' restriction.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L178
ResourceNameRestriction The resource name parameter 'resourceName' should be defined with a 'pattern' restriction.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L388
ResourceNameRestriction The resource name parameter 'resourceName' should be defined with a 'pattern' restriction.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L436
MissingTypeObject The schema 'Identity' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L575
MissingTypeObject The schema 'IdentityUpdate' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L607
MissingTypeObject The schema 'SystemAssignedIdentity' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L643
TrackedResourcesMustHavePut The tracked resource SystemAssignedIdentity does not have a corresponding put operation.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L643
GuidUsage Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L690
GuidUsage Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L696
GuidUsage Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L702
GuidUsage Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L720
GuidUsage Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L726
GuidUsage Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L732
MissingTypeObject The schema 'UserAssignedIdentitiesListResult' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L785
MissingTypeObject The schema 'CloudError' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L801
MissingTypeObject The schema 'CloudErrorBody' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L811
MissingTypeObject The schema 'OperationDisplay' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L856
MissingTypeObject The schema 'OperationListResult' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L882
XmsParameterLocation The parameter 'SubscriptionIdParameter' is defined in global parameters section without 'x-ms-parameter-location' extension. This would add the parameter as the client property. Please ensure that this is exactly you want. If so, apply the extension 'x-ms-parameter-location': 'client'. Else, apply the extension 'x-ms-parameter-location': 'method'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L915
XmsParameterLocation The parameter 'ApiVersionParameter' is defined in global parameters section without 'x-ms-parameter-location' extension. This would add the parameter as the client property. Please ensure that this is exactly you want. If so, apply the extension 'x-ms-parameter-location': 'client'. Else, apply the extension 'x-ms-parameter-location': 'method'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L938
⚠️ ReservedResourceNamesModelAsEnum The service-defined (reserved name) resource 'default' should be represented as a path parameter enum with modelAsString set to true.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L37
⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'scope'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L46
⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L46
⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'resourceGroupName'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L46
⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L46
⚠️ UniqueXmsExample Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: MsiOperationsList
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L74
⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'scope'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L79
⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
Location: Microsoft.ManagedIdentity/preview/2023-07-31-preview/ManagedIdentity.json#L79
️️✔️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?

Copy link

openapi-pipeline-app bot commented Nov 30, 2023

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-js - @azure/arm-msi - Approved - 3.0.0
+	Class ManagedServiceIdentityClient has a new signature
️️✔️ azure-sdk-for-net-track2 succeeded [Detail] [Expand]
  • ️✔️Succeeded [Logs] Generate from e599db212ebe5c87149d1dad69c04a530766ebf3. 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.ManagedServiceIdentities [View full logs]  [Preview SDK Changes]
    info	[Changelog]
️⚠️ azure-sdk-for-python-track2 warning [Detail]
  • ⚠️Warning [Logs] Generate from e599db212ebe5c87149d1dad69c04a530766ebf3. 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: azure-devtools 1.2.1 does not provide the extra 'ci-tools'
    cmderr	[automation_init.sh] WARNING: azure-devtools 1.2.1 does not provide the extra 'ci-tools'
    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! 9.8.1 -> 10.2.4
    cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.2.4>
    cmderr	[automation_generate.sh] npm notice Run `npm install -g npm@10.2.4` to update!
    cmderr	[automation_generate.sh] npm notice
  • ️✔️track2_azure-mgmt-msi [View full logs]  [Preview SDK Changes]
    info	[Changelog]
️⚠️ azure-sdk-for-java warning [Detail]
  • ⚠️Warning [Logs] Generate from e599db212ebe5c87149d1dad69c04a530766ebf3. 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 is available: 23.0.1 -> 23.3.1
    cmderr	[init.sh] [notice] To update, run: pip install --upgrade pip
    cmderr	[init.sh] [notice] A new release of pip is available: 23.0.1 -> 23.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-msi-generated [View full logs]  [Preview SDK Changes]
️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
  • ️✔️Succeeded [Logs] Generate from e599db212ebe5c87149d1dad69c04a530766ebf3. 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/msi/armmsi [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-js succeeded [Detail] [Expand]
  • ️✔️Succeeded [Logs] Generate from e599db212ebe5c87149d1dad69c04a530766ebf3. 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-msi [View full logs]  [Preview SDK Changes] Breaking Change Detected
    info	[Changelog] **Breaking Changes**
    info	[Changelog]
    info	[Changelog]   - Class ManagedServiceIdentityClient has a new signature
️⚠️ azure-resource-manager-schemas warning [Detail]
  • ⚠️Warning [Logs] Generate from e599db212ebe5c87149d1dad69c04a530766ebf3. 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]
    cmderr	[initScript.sh] npm notice New major version of npm available! 8.19.4 -> 10.2.4
    cmderr	[initScript.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.2.4>
    cmderr	[initScript.sh] npm notice Run `npm install -g npm@10.2.4` 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
️❌ azure-powershell failed [Detail]
  • Pipeline Framework Failed [Logs] Generate from e599db212ebe5c87149d1dad69c04a530766ebf3. 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
    SSL error: syscall failure: Broken pipe
    Error: SSL error: syscall failure: Broken pipe
  • ️✔️Az.msi.DefaultTag [View full logs
    error	Fatal error: SSL error: syscall failure: Broken pipe
    error	The following packages are still pending:
    error		Az.msi.DefaultTag
Posted by Swagger Pipeline | How to fix these errors?

Copy link

openapi-pipeline-app bot commented Nov 30, 2023

Generated ApiView

Language Package Name ApiView Link
Go sdk/resourcemanager/msi/armmsi There is no API change compared with the previous version
Java azure-resourcemanager-msi-generated https://apiview.dev/Assemblies/Review/071b82154ed64c639e80e4a3ea18ea7a
.Net Azure.ResourceManager.ManagedServiceIdentities There is no API change compared with the previous version
JavaScript @azure/arm-msi https://apiview.dev/Assemblies/Review/177a4f4c41c647e7b5176704e5be3701
Swagger Microsoft.ManagedIdentity https://apiview.dev/Assemblies/Review/b8299546d22c451f8c74a3b1a61a82db

Copy link

Hi @RamyaElangovanP! For review efficiency consideration, when creating a new API version, it is required to place API specs of the base version in the first commit, and push new version updates into successive commits. You can use OpenAPIHub to initialize the PR for adding a new version.
For more details refer to the wiki.

@RamyaElangovanP
Copy link
Contributor Author

pr/ RequestMerge

@AzureRestAPISpecReview AzureRestAPISpecReview added the ReadyForApiTest <valid label in PR review process>add this label when swagger and service APIs are ready for test label Dec 5, 2023
@RamyaElangovanP
Copy link
Contributor Author

/pr RequestMerge

@visingla-ms visingla-ms merged commit f0614ca into Azure:main Dec 5, 2023
29 of 30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Approved-SdkBreakingChange-JavaScript ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review CI-BreakingChange-JavaScript CI-MissingBaseCommit new-api-version ReadyForApiTest <valid label in PR review process>add this label when swagger and service APIs are ready for test resource-manager
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants