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

[EventHubs]: Adding missing descriptions #21685

Merged
merged 4 commits into from
Nov 29, 2022

Conversation

damodaravadhani
Copy link
Member

@damodaravadhani damodaravadhani commented Nov 29, 2022

ARM API Information (Control Plane)

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

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.
  3. When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
  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, @damodaravadhani 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 Nov 29, 2022

    Swagger Validation Report

    ️️✔️BreakingChange succeeded [Detail] [Expand]
    There are no breaking changes.
    compared swaggers (via Oad v0.10.2)] new version base version
    SchemaRegistry.json 2022-01-01-preview(a979ded) 2022-01-01-preview(main)
    namespaces-preview.json 2022-01-01-preview(a979ded) 2022-01-01-preview(main)
    SchemaRegistry.json 2021-11-01(a979ded) 2021-11-01(main)
    namespaces-preview.json 2021-11-01(a979ded) 2021-11-01(main)
    ️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️⚠️LintDiff: 0 Warnings warning [Detail]
    compared tags (via openapi-validator v2.0.0) new version base version
    package-2021-11 package-2021-11(a979ded) package-2021-11(main)
    package-2022-01-preview package-2022-01-preview(a979ded) package-2022-01-preview(main)

    The following errors/warnings exist before current PR submission:

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

    Rule Message
    ResourceNameRestriction The resource name parameter 'namespaceName' should be defined with a 'pattern' restriction.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L118
    CreateOperationAsyncResponseValidation An async PUT operation must set long running operation options 'x-ms-long-running-operation-options'
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L119
    LongRunningResponseStatusCode A 'put' operation 'Namespaces_CreateOrUpdate' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 201.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L119
    CreateOperationAsyncResponseValidation Only 201 is the supported response code for PUT async response.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L169
    LroLocationHeader A 202 response should include an Location response header.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L169
    DeleteOperationAsyncResponseValidation An async DELETE operation must set long running operation options 'x-ms-long-running-operation-options'
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L181
    LroLocationHeader A 202 response should include an Location response header.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L210
    UnSupportedPatchProperties The patch operation body parameter schema should not contains property name.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L283
    UnSupportedPatchProperties The patch operation body parameter schema should not contains property type.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L283
    UnSupportedPatchProperties The patch operation body parameter schema should not contains property location.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L283
    LroLocationHeader A 202 response should include an Location response header.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L312
    ResourceNameRestriction The resource name parameter 'namespaceName' should be defined with a 'pattern' restriction.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L324
    ResourceNameRestriction The resource name parameter 'namespaceName' should be defined with a 'pattern' restriction.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L372
    ResourceNameRestriction The resource name parameter 'privateEndpointConnectionName' should be defined with a 'pattern' restriction.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L372
    TrackedResourcePatchOperation Tracked resource 'PrivateEndpointConnection' must have patch operation that at least supports the update of tags.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L372
    CreateOperationAsyncResponseValidation Only 201 is the supported response code for PUT async response.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L426
    LroLocationHeader A 202 response should include an Location response header.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L426
    DeleteOperationAsyncResponseValidation An async DELETE operation must set long running operation options 'x-ms-long-running-operation-options'
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L440
    LroLocationHeader A 202 response should include an Location response header.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L475
    ResourceNameRestriction The resource name parameter 'namespaceName' should be defined with a 'pattern' restriction.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L537
    ResourceNameRestriction The resource name parameter 'namespaceName' should be defined with a 'pattern' restriction.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L582
    ResourceNameRestriction The resource name parameter 'namespaceName' should be defined with a 'pattern' restriction.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L624
    ResourceNameRestriction The resource name parameter 'resourceAssociationName' should be defined with a 'pattern' restriction.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L624
    PostOperationAsyncResponseValidation An async POST operation must set long running operation options 'x-ms-long-running-operation-options'
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L625
    LroLocationHeader A 202 response should include an Location response header.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L657
    MissingTypeObject The schema 'EHNamespaceListResult' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L672
    MissingTypeObject The schema 'EHNamespace' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L688
    MissingTypeObject The schema 'properties' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L703
    MissingTypeObject The schema 'Identity' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L857
    MissingTypeObject The schema 'Encryption' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L912
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
    ️⚠️~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]

    API Test is not triggered due to precheck failure. Check pipeline log for details.

    ️️✔️~[Staging] SwaggerAPIView succeeded [Detail] [Expand]
    ️❌ModelValidation: 6 Errors, 0 Warnings failed [Detail]
    Rule Message
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L206:22
    ExampleUrl: 2022-01-01-preview/examples/NameSpaces/EHNameSpaceDelete.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L471:22
    ExampleUrl: 2022-01-01-preview/examples/NameSpaces/PrivateEndPointConnectionDelete.json
    MISSING_RESOURCE_ID id is required to return in response of GET/PUT resource calls but not being provided
    Url: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L1147:46
    ExampleUrl: 2022-01-01-preview/examples/NameSpaces/NetworkSecurityPerimeterConfigurationList.json#L12:11
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.EventHub/preview/2022-01-01-preview/namespaces-preview.json#L653:22
    ExampleUrl: 2022-01-01-preview/examples/NameSpaces/NetworkSecurityPerimeterConfigurationReconcile.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.EventHub/stable/2021-11-01/namespaces-preview.json#L206:22
    ExampleUrl: 2021-11-01/examples/NameSpaces/EHNameSpaceDelete.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.EventHub/stable/2021-11-01/namespaces-preview.json#L465:22
    ExampleUrl: 2021-11-01/examples/NameSpaces/PrivateEndPointConnectionDelete.json
    ️️✔️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.
    ️️✔️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 Nov 29, 2022

    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]
    ️⚠️ azure-sdk-for-python-track2 warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from d85953a. 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 major version of npm available! 8.19.2 -> 9.1.2
      cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.1.2>
      cmderr	[automation_generate.sh] npm notice Run `npm install -g npm@9.1.2` to update!
      cmderr	[automation_generate.sh] npm notice
    • ️✔️track2_azure-mgmt-eventhub [View full logs]  [Release SDK Changes]
      info	[Changelog]
    ️⚠️ azure-sdk-for-java warning [Detail]
    ️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from d85953a. 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/eventhub/armeventhub [View full logs]  [Release 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]Release - Generate from d85953a. 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-eventhub [View full logs]  [Release SDK Changes]
      info	[Changelog] **Features**
      info	[Changelog]
      info	[Changelog]   - Added operation group ApplicationGroupOperations
      info	[Changelog]   - Added operation group NetworkSecurityPerimeterConfigurationOperations
      info	[Changelog]   - Added operation group NetworkSecurityPerimeterConfigurations
      info	[Changelog]   - Added Interface ApplicationGroup
      info	[Changelog]   - Added Interface ApplicationGroupCreateOrUpdateApplicationGroupOptionalParams
      info	[Changelog]   - Added Interface ApplicationGroupDeleteOptionalParams
      info	[Changelog]   - Added Interface ApplicationGroupGetOptionalParams
      info	[Changelog]   - Added Interface ApplicationGroupListByNamespaceNextOptionalParams
      info	[Changelog]   - Added Interface ApplicationGroupListByNamespaceOptionalParams
      info	[Changelog]   - Added Interface ApplicationGroupListResult
      info	[Changelog]   - Added Interface ApplicationGroupPolicy
      info	[Changelog]   - Added Interface NetworkSecurityPerimeter
      info	[Changelog]   - Added Interface NetworkSecurityPerimeterConfiguration
      info	[Changelog]   - Added Interface NetworkSecurityPerimeterConfigurationList
      info	[Changelog]   - Added Interface NetworkSecurityPerimeterConfigurationListOptionalParams
      info	[Changelog]   - Added Interface NetworkSecurityPerimeterConfigurationPropertiesProfile
      info	[Changelog]   - Added Interface NetworkSecurityPerimeterConfigurationPropertiesResourceAssociation
      info	[Changelog]   - Added Interface NetworkSecurityPerimeterConfigurationsCreateOrUpdateOptionalParams
      info	[Changelog]   - Added Interface NspAccessRule
      info	[Changelog]   - Added Interface NspAccessRuleProperties
      info	[Changelog]   - Added Interface NspAccessRulePropertiesSubscriptionsItem
      info	[Changelog]   - Added Interface ProvisioningIssue
      info	[Changelog]   - Added Interface ProvisioningIssueProperties
      info	[Changelog]   - Added Interface ThrottlingPolicy
      info	[Changelog]   - Added Type Alias ApplicationGroupCreateOrUpdateApplicationGroupResponse
      info	[Changelog]   - Added Type Alias ApplicationGroupGetResponse
      info	[Changelog]   - Added Type Alias ApplicationGroupListByNamespaceNextResponse
      info	[Changelog]   - Added Type Alias ApplicationGroupListByNamespaceResponse
      info	[Changelog]   - Added Type Alias ApplicationGroupPolicyType
      info	[Changelog]   - Added Type Alias ApplicationGroupPolicyUnion
      info	[Changelog]   - Added Type Alias MetricId
      info	[Changelog]   - Added Type Alias NetworkSecurityPerimeterConfigurationListResponse
      info	[Changelog]   - Added Type Alias NetworkSecurityPerimeterConfigurationProvisioningState
      info	[Changelog]   - Added Type Alias NspAccessRuleDirection
      info	[Changelog]   - Added Type Alias PublicNetworkAccess
      info	[Changelog]   - Added Type Alias ResourceAssociationAccessMode
      info	[Changelog]   - Added Type Alias TlsVersion
      info	[Changelog]   - Interface Cluster has a new optional parameter supportsScaling
      info	[Changelog]   - Interface EHNamespace has a new optional parameter minimumTlsVersion
      info	[Changelog]   - Interface EHNamespace has a new optional parameter publicNetworkAccess
      info	[Changelog]   - Class EventHubManagementClient has a new parameter applicationGroupOperations
      info	[Changelog]   - Class EventHubManagementClient has a new parameter networkSecurityPerimeterConfigurationOperations
      info	[Changelog]   - Class EventHubManagementClient has a new parameter networkSecurityPerimeterConfigurations
      info	[Changelog]   - Added Enum KnownApplicationGroupPolicyType
      info	[Changelog]   - Added Enum KnownMetricId
      info	[Changelog]   - Added Enum KnownNetworkSecurityPerimeterConfigurationProvisioningState
      info	[Changelog]   - Added Enum KnownNspAccessRuleDirection
      info	[Changelog]   - Added Enum KnownPublicNetworkAccess
      info	[Changelog]   - Added Enum KnownResourceAssociationAccessMode
      info	[Changelog]   - Added Enum KnownTlsVersion
      info	[Changelog]   - Enum KnownPublicNetworkAccessFlag has a new value SecuredByPerimeter
    ️⚠️ azure-resource-manager-schemas warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from d85953a. 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]  WARN 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
      warn	No file changes detected after generation
    • ️✔️eventhub [View full logs
    ️️✔️ azure-powershell succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from d85953a. 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.EventHub [View full logs]  [Release SDK Changes]
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Nov 29, 2022

    Generated ApiView

    Language Package Name ApiView Link
    Go sdk/resourcemanager/eventhub/armeventhub Create ApiView failed. Please ensure your github account in Azure/Microsoft is public and add a comment "/azp run" to re-trigger the CI.
    Python track2_azure-mgmt-eventhub Create ApiView failed. Please ensure your github account in Azure/Microsoft is public and add a comment "/azp run" to re-trigger the CI.
    JavaScript @azure/arm-eventhub Create ApiView failed. Please ensure your github account in Azure/Microsoft is public and add a comment "/azp run" to re-trigger the CI.
    Java azure-resourcemanager-eventhubs-generated Create ApiView failed. Please ensure your github account in Azure/Microsoft is public and add a comment "/azp run" to re-trigger the CI.
    .Net Azure.ResourceManager.EventHubs Create ApiView failed. Please ensure your github account in Azure/Microsoft is public and add a comment "/azp run" to re-trigger the CI.

    @ghost ghost added the Event Hubs label Nov 29, 2022
    @openapi-workflow-bot
    Copy link

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

    anandanthony pushed a commit to anandMicro/azure-rest-api-specs that referenced this pull request Dec 16, 2022
    * Adding missing descriptions
    
    * fix
    
    * Doc Fix
    
    * Fixes
    kayousef-zz pushed a commit to kayousef-zz/azure-rest-api-specs that referenced this pull request Dec 21, 2022
    * Adding missing descriptions
    
    * fix
    
    * Doc Fix
    
    * Fixes
    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.

    3 participants