Skip to content

User/osaghaso/adding router job#24153

Merged
JoshLove-msft merged 34 commits intomainfrom
user/osaghaso/adding_router_job
Oct 6, 2023
Merged

User/osaghaso/adding router job#24153
JoshLove-msft merged 34 commits intomainfrom
user/osaghaso/adding_router_job

Conversation

@osaghaso
Copy link
Copy Markdown
Contributor

Data Plane API - Pull Request

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):
link to Schema

  • 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:

❔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.

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

Tooling

Guidelines & Specifications

Helpful Links

@openapi-workflow-bot
Copy link
Copy Markdown

Hi, @osaghaso 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
    Copy Markdown

    openapi-pipeline-app bot commented May 24, 2023

    Swagger Validation Report

    ️️✔️BreakingChange succeeded [Detail] [Expand]
    There are no breaking changes.
    compared swaggers (via Oad v0.10.4)] new version base version
    AzureCommunicationServices.json 2018-01-01(02e9ba1) 2018-01-01(main)
    ️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️⚠️LintDiff: 2 Warnings warning [Detail]
    compared tags (via openapi-validator v2.1.6) new version base version
    package-2023-06-01-preview package-2023-06-01-preview(02e9ba1) package-2023-06-01-preview(main)

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

    Rule Message Related RPC [For API reviewers]
    ⚠️ 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: Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json#L343
    ⚠️ 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: Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json#L467


    The following errors/warnings exist before current PR submission:

    Rule Message
    IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json#L1688
    IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json#L1692
    ⚠️ AdditionalPropertiesObject additionalProperties with type object is a common error.
    Location: Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json#L963
    ⚠️ PropertyDescription Property should have a description.
    Location: Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json#L963
    ⚠️ AdditionalPropertiesObject additionalProperties with type object is a common error.
    Location: Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json#L992
    ⚠️ PropertyDescription Property should have a description.
    Location: Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json#L992
    ⚠️ AdditionalPropertiesObject additionalProperties with type object is a common error.
    Location: Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json#L1066
    ⚠️ PropertyDescription Property should have a description.
    Location: Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json#L1066
    ⚠️ AdditionalPropertiesObject additionalProperties with type object is a common error.
    Location: Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json#L1093
    ⚠️ PropertyDescription Property should have a description.
    Location: Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json#L1093
    ️️✔️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.
    ️️✔️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).
    ️️✔️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
    Copy link
    Copy Markdown

    openapi-pipeline-app bot commented May 24, 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 succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from c280892. 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.Messaging.EventGrid [View full logs]  [Release SDK Changes]
      info	[Changelog]
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link
    Copy Markdown

    openapi-pipeline-app bot commented May 24, 2023

    Generated ApiView

    Language Package Name ApiView Link
    .Net Azure.Messaging.EventGrid https://apiview.dev/Assemblies/Review/ca60b2d2705c47e1bbbb67dbb15e92d2

    @openapi-workflow-bot
    Copy link
    Copy Markdown

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

    }
    ],
    "properties": {
    "queueInfo": {
    Copy link
    Copy Markdown
    Member

    Choose a reason for hiding this comment

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

    Can this still be renamed? If so we should use queueDetails. If not we can add "x-ms-client-name" and set it to queueDetails.

    @heaths
    Copy link
    Copy Markdown
    Member

    heaths commented Oct 6, 2023

    There are conflicts from preventing this from being merged, and since this is going to main, that means it's ready for a final review. Have you scheduled a review with the REST API Stewardship Board? Otherwise, if it's a work in progress, you should use a feature branch. See https://eng.ms/docs/products/azure-developer-experience/onboard/requirements.

    @JoshLove-msft
    Copy link
    Copy Markdown
    Member

    There are conflicts from preventing this from being merged, and since this is going to main, that means it's ready for a final review. Have you scheduled a review with the REST API Stewardship Board? Otherwise, if it's a work in progress, you should use a feature branch. See https://eng.ms/docs/products/azure-developer-experience/onboard/requirements.

    These events have already been reviewed by the arch board - they don't go through a REST API review.

    @openapi-pipeline-app
    Copy link
    Copy Markdown

    Swagger pipeline restarted successfully, please wait for status update in this comment.

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

    Projects

    None yet

    Development

    Successfully merging this pull request may close these issues.

    6 participants