Skip to content

Comments

[Hub Generated] Review request for Microsoft.Network to add version stable/2022-04-01#22357

Merged
lirenhe merged 8 commits intomainfrom
imsiddhartha-trafficmanager-Microsoft.Network-2022-04-01
May 25, 2023
Merged

[Hub Generated] Review request for Microsoft.Network to add version stable/2022-04-01#22357
lirenhe merged 8 commits intomainfrom
imsiddhartha-trafficmanager-Microsoft.Network-2022-04-01

Conversation

@imsiddhartha
Copy link
Contributor

@imsiddhartha imsiddhartha commented Jan 30, 2023

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.

ARM API Information (Control Plane)

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

Changelog

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

  1. What's the purpose of the update?
    • new service onboarding
    • new API version
    • update existing version for new feature
    • update existing version to fix swagger quality issue in s360
    • Other, please clarify
  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. Mar 2023
  3. When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month. Feb
  4. By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

Applicability: ⚠️

If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

  • Change to data plane APIs
  • Adding new properties
  • All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

  • Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

    • Adding a new service
    • Adding new API(s)
    • Adding a new API version
      • To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.
  • Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

  • If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist

If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.

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

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

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

@openapi-workflow-bot
Copy link

Hi, @imsiddhartha 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
    Copy link

    openapi-pipeline-app bot commented Jan 30, 2023

    Swagger Validation Report

    ️️✔️BreakingChange succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
    There are no breaking changes.
    compared swaggers (via Oad v0.10.4)] new version base version
    trafficmanager.json 2022-04-01(530821c) 2018-08-01(main)
    trafficmanager.json 2022-04-01(530821c) 2022-04-01-preview(main)
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️⚠️LintDiff: 34 Warnings warning [Detail]
    compared tags (via openapi-validator v2.1.2) new version base version
    package-2022-04 package-2022-04(530821c) default(main)

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

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

    Rule Message Related RPC [For API reviewers]
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L25
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L25
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L101
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L101
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L174
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L174
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L268
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L268
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L340
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L340
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L385
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L385
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L436
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L436
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L478
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L478
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L514
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L514
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L564
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L564
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L638
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L638
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L685
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L685
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L740
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L740
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L773
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L773
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'subscriptionId'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L869
    ⚠️ ParameterNotUsingCommonTypes Not using the common-types defined parameter 'api-version'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L869


    The following errors/warnings exist before current PR submission:

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

    Rule Message
    OperationsAPIImplementation Operations API must be implemented for 'Microsoft.Network'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L1
    PathForNestedResource The path for nested resource doest not meet the valid resource pattern.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L18
    ResourceNameRestriction The resource name parameter 'profileName' should be defined with a 'pattern' restriction.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L18
    ResourceNameRestriction The resource name parameter 'endpointName' should be defined with a 'pattern' restriction.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L18
    UnSupportedPatchProperties The patch operation body parameter schema should not contains property name.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L59
    UnSupportedPatchProperties The patch operation body parameter schema should not contains property type.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L59
    DeleteResponseBodyEmpty The delete response body must be empty.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L312
    GetCollectionOnlyHasValueAndNextLink Get endpoints for collections of resources must only have the value and nextLink properties in their model.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L450
    GetCollectionOnlyHasValueAndNextLink Get endpoints for collections of resources must only have the value and nextLink properties in their model.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L489
    ResourceNameRestriction The resource name parameter 'profileName' should be defined with a 'pattern' restriction.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L507
    DeleteResponseBodyEmpty The delete response body must be empty.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L659
    UnSupportedPatchProperties The patch operation body parameter schema should not contains property name.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L696
    UnSupportedPatchProperties The patch operation body parameter schema should not contains property type.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L696
    UnSupportedPatchProperties The patch operation body parameter schema should not contains property location.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L696
    GetCollectionOnlyHasValueAndNextLink Get endpoints for collections of resources must only have the value and nextLink properties in their model.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L748
    ResourceNameRestriction The resource name parameter 'profileName' should be defined with a 'pattern' restriction.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L766
    ParametersInPointGet Query parameter topLeft should be removed. Point Get's MUST not have query parameters other than api version.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L773
    ParametersInPointGet Query parameter botRight should be removed. Point Get's MUST not have query parameters other than api version.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L773
    PathForPutOperation The path for 'put' operation must be under a subscription and resource group.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L862
    GetCollectionOnlyHasValueAndNextLink Get endpoints for collections of resources must only have the value and nextLink properties in their model.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L880
    PutResponseSchemaDescription Any Put MUST contain 200 and 201 return codes.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L911
    DeleteOperationResponses The delete operation is defined without a 200 or 204 error response implementation,please add it.'
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L945
    DeleteResponseBodyEmpty The delete response body must be empty.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L948
    MissingTypeObject The schema 'DeleteOperationResult' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L968
    MissingTypeObject The schema 'EndpointProperties' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L979
    XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L1054
    IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L1067
    XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L1076
    MissingTypeObject The schema 'HeatMapModel' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L1109
    NestedResourcesMustHaveListOperation The nested resource 'HeatMapModel' does not have list operation, please add it.
    Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L1109
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
    ️❌~[Staging] ServiceAPIReadinessTest: 0 Errors, 0 Warnings failed [Detail]

    Tag package-2022-04; Prod region: Not deployed; Canary region: Not deployed

    ️️✔️SwaggerAPIView succeeded [Detail] [Expand]
    ️️✔️CadlAPIView 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.
    ️️✔️PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️️✔️SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    ️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
    Validation passes for Lint(RPaaS).
    ️️✔️CadlValidation succeeded [Detail] [Expand]
    Validation passes for CadlValidation.
    ️️✔️TypeSpec Validation succeeded [Detail] [Expand]
    Validation passes for TypeSpec Validation.
    ️️✔️PR Summary succeeded [Detail] [Expand]
    Validation passes for Summary.
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Jan 30, 2023

    Swagger Generation Artifacts

    ️️✔️ApiDocPreview succeeded [Detail] [Expand]
     Please click here to preview with your @microsoft account. 
    ️️✔️SDK Breaking Change Tracking succeeded [Detail] [Expand]

    Breaking Changes Tracking



    ️❌ azure-sdk-for-net-track2 failed [Detail]
    • Failed [Logs]Release - Generate from 4f4073b. 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
      cmderr	[Invoke-GenerateAndBuildV2.ps1] �[31;1mGeneratePackage: �[0m/mnt/vss/_work/1/s/azure-sdk-for-net/eng/scripts/automation/GenerateAndBuildLib.ps1:712
      cmderr	[Invoke-GenerateAndBuildV2.ps1] �[36;1mLine |
      cmderr	[Invoke-GenerateAndBuildV2.ps1] �[36;1m 712 | �[0m         �[36;1mGeneratePackage -projectFolder $projectFolder -sdkRootPath $s�[0m …
      cmderr	[Invoke-GenerateAndBuildV2.ps1] �[36;1m     | �[31;1m         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      cmderr	[Invoke-GenerateAndBuildV2.ps1] �[31;1m�[36;1m     | �[31;1mFailed to build sdk. exit code: False
      cmderr	[Invoke-GenerateAndBuildV2.ps1] �[0m
    • Azure.ResourceManager.TrafficManager [View full logs]  [Release SDK Changes] Breaking Change Detected
      info	[Changelog] Breaking Changes: /home/cloudtest/.nuget/packages/microsoft.dotnet.apicompat/5.0.0-beta.20467.1/build/Microsoft.DotNet.ApiCompat.targets(82,5): error : TypesMustExist : Type 'Azure.ResourceManager.TrafficManager.Models.TrafficManagerRelativeDnsNameAvailabilityContent' does not exist in the implementation but it does exist in the contract. [/mnt/vss/_work/1/s/azure-sdk-for-net/sdk/trafficmanager/Azure.ResourceManager.TrafficManager/src/Azure.ResourceManager.TrafficManager.csproj::TargetFramework=netstandard2.0],
      info	[Changelog] /home/cloudtest/.nuget/packages/microsoft.dotnet.apicompat/5.0.0-beta.20467.1/build/Microsoft.DotNet.ApiCompat.targets(96,5): error : ApiCompat failed for '/mnt/vss/_work/1/s/azure-sdk-for-net/artifacts/bin/Azure.ResourceManager.TrafficManager/Debug/netstandard2.0/Azure.ResourceManager.TrafficManager.dll' [/mnt/vss/_work/1/s/azure-sdk-for-net/sdk/trafficmanager/Azure.ResourceManager.TrafficManager/src/Azure.ResourceManager.TrafficManager.csproj::TargetFramework=netstandard2.0]
    ️⚠️ azure-sdk-for-python-track2 warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from 4f4073b. SDK Automation 14.0.0
      command	sh scripts/automation_init.sh ../azure-sdk-for-python_tmp/initInput.json ../azure-sdk-for-python_tmp/initOutput.json
      cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
      command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
      cmderr	[automation_generate.sh]
      cmderr	[automation_generate.sh] npm notice New minor version of npm available! 9.5.1 -> 9.6.7
      cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.7>
      cmderr	[automation_generate.sh] npm notice Run `npm install -g npm@9.6.7` to update!
      cmderr	[automation_generate.sh] npm notice
    • ️✔️track2_azure-mgmt-trafficmanager [View full logs]  [Release SDK Changes]
      info	[Changelog] ### Features Added
      info	[Changelog]
      info	[Changelog]   - Added operation ProfilesOperations.check_traffic_manager_name_availability_v2
      info	[Changelog]   - Model Endpoint has a new parameter always_serve
    ️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from 4f4073b. 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-trafficmanager [View full logs]  [Release SDK Changes]
      info	[Changelog] **Features**
      info	[Changelog]
      info	[Changelog]   - Added operation Profiles.checkTrafficManagerNameAvailabilityV2
      info	[Changelog]   - Added Interface Endpoint
      info	[Changelog]   - Added Interface HeatMapModel
      info	[Changelog]   - Added Interface Profile
      info	[Changelog]   - Added Interface ProfilesCheckTrafficManagerNameAvailabilityV2OptionalParams
      info	[Changelog]   - Added Interface ProxyResource
      info	[Changelog]   - Added Interface TrackedResource
      info	[Changelog]   - Added Interface TrafficManagerGeographicHierarchy
      info	[Changelog]   - Added Interface UserMetricsModel
      info	[Changelog]   - Added Type Alias AlwaysServe
      info	[Changelog]   - Added Type Alias ProfilesCheckTrafficManagerNameAvailabilityV2Response
      info	[Changelog]   - Added Enum KnownAlwaysServe
      info	[Changelog]   - Enum KnownEndpointMonitorStatus has a new value Unmonitored
      info	[Changelog]   - Added function getContinuationToken
    ️⚠️ azure-resource-manager-schemas warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from 4f4073b. 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
    • ️✔️trafficmanager [View full logs]  [Release Schema Changes]
    ️❌ azure-powershell failed [Detail]
    • Pipeline Framework Failed [Logs]Release - Generate from 4f4073b. 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.trafficmanager.DefaultTag [View full logs
      error	Fatal error: SSL error: syscall failure: Broken pipe
      error	The following packages are still pending:
      error		Az.trafficmanager.DefaultTag
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Jan 30, 2023

    Generated ApiView

    Language Package Name ApiView Link
    .Net Azure.ResourceManager.TrafficManager https://apiview.dev/Assemblies/Review/75984f826f944d83b434b95f32bd22b2
    JavaScript @azure/arm-trafficmanager https://apiview.dev/Assemblies/Review/3f6898db79864e4e81e5079c94660f3b

    Copy link

    @jblinkedin jblinkedin left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    LGTM

    @imsiddhartha imsiddhartha marked this pull request as ready for review January 31, 2023 06:29
    @openapi-workflow-bot openapi-workflow-bot bot added ARMReview WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jan 31, 2023
    @openapi-workflow-bot
    Copy link

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

    @openapi-workflow-bot
    Copy link

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

    TaskHow to fixPriority
    AvocadoFix-AvocadoHigh
    Semantic validationFix-SemanticValidation-ErrorHigh
    Model validationFix-ModelValidation-ErrorHigh
    LintDiffFix-LintDiffhigh
    If you need further help, please feedback via swagger feedback.

    @sjanamma
    Copy link

    sjanamma commented Feb 1, 2023

    @imsiddhartha - Please fix the two linter errors introduced as part of this api-version change. https://github.com/Azure/azure-rest-api-specs/pull/22357/checks?check_run_id=11012171989

    @imsiddhartha
    Copy link
    Contributor Author

    @akning-ms Fixed prettier checks

    @fengzhou-msft
    Copy link
    Member

    The azure-sdk-for-net-track2 failure is caused by a breaking change where the conditon for auto-renaming from TrafficManagerRelativeDnsNameAvailabilityParameters to TrafficManagerRelativeDnsNameAvailabilityContent is no longer established . We will use config to name it back. The failure should not block this PR.

    @akning-ms
    Copy link
    Contributor

    Hi @imsiddhartha, ping me for merge when your service is almost ready in production (like before about 1 weeks). according to API readiness check. Looks the new version is not deployed in production yet.

    @akning-ms akning-ms added the Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates label Mar 3, 2023
    @ghost
    Copy link

    ghost commented Mar 19, 2023

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

    @ghost ghost added the no-recent-activity label Mar 19, 2023
    @ghost ghost closed this Apr 3, 2023
    @ghost
    Copy link

    ghost commented Apr 3, 2023

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

    @jblinkedin
    Copy link

    Reopening as we are ready to GET this released.

    @ghost
    Copy link

    ghost commented May 7, 2023

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

    @ghost ghost added the no-recent-activity label May 7, 2023
    @akning-ms akning-ms assigned raych1 and unassigned akning-ms May 22, 2023
    @akning-ms
    Copy link
    Contributor

    re-assign to Ray as seems I don't have merge permission anymore

    @ghost ghost removed the no-recent-activity label May 22, 2023
    @lirenhe
    Copy link
    Member

    lirenhe commented May 25, 2023

    /azp run

    @imsiddhartha
    Copy link
    Contributor Author

    /azp run unifiedPipeline

    @azure-pipelines
    Copy link

    No pipelines are associated with this pull request.

    @azure-pipelines
    Copy link

    Azure Pipelines successfully started running 1 pipeline(s).

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Labels

    Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review Network - Traffic Manager 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.

    8 participants