Skip to content

Event Hubs: reverted removal of Messaging plan from namespace#2831

Closed
v-Ajnava wants to merge 1 commit intoAzure:masterfrom
v-Ajnava:masterEHMessagingplan
Closed

Event Hubs: reverted removal of Messaging plan from namespace#2831
v-Ajnava wants to merge 1 commit intoAzure:masterfrom
v-Ajnava:masterEHMessagingplan

Conversation

@v-Ajnava
Copy link
Contributor

@v-Ajnava v-Ajnava commented Apr 6, 2018

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

@AutorestCI
Copy link

AutorestCI commented Apr 6, 2018

Automation for azure-sdk-for-python

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-python#2051

@AutorestCI
Copy link

AutorestCI commented Apr 6, 2018

Automation for azure-sdk-for-node

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-node#2658

@AutorestCI
Copy link

AutorestCI commented Apr 6, 2018

Automation for azure-libraries-for-java

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
AutorestCI/azure-libraries-for-java#53

@AutorestCI
Copy link

AutorestCI commented Apr 6, 2018

Automation for azure-sdk-for-go

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-go#1506

"MessagingPlan"
],
"operationId": "Namespaces_MessagingPlanGet",
"description": "Gets a description for the specified namespace.",
Copy link
Contributor

Choose a reason for hiding this comment

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

Gets a description for the specified namespace. [](start = 24, length = 47)

Please fix the description. Seems to be copied from somewhere else.

"tags": [
"MessagingPlan"
],
"operationId": "Namespaces_MessagingPlanGet",
Copy link
Contributor

Choose a reason for hiding this comment

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

Namespaces_MessagingPlanGet [](start = 24, length = 27)

change the name to - Namespaces_GetMessagingPlan

},
"description": "The response of the List MessagingRegions operation."
},
"MessagingPlanproperties": {
Copy link
Contributor

Choose a reason for hiding this comment

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

MessagingPlanproperties [](start = 2, length = 23)

Properties should start with capital P

},
"description": "The response of the List MessagingRegions operation."
},
"MessagingPlanproperties": {
Copy link
Contributor

Choose a reason for hiding this comment

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

MessagingPlanproperties [](start = 2, length = 23)

this entire type is only used as service return type. Please mark each property as "readOnly": true

"description": "revision number"
}
},
"description": "Messaging Region"
Copy link
Contributor

Choose a reason for hiding this comment

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

Messaging Region [](start = 22, length = 16)

Please add better description of the model. I'm not clear how this model even relates to regions. The only exposed operation in the swagger is "Get" on Messaging plan which suggests that there should be only one Messaging plan per namespace. Did you miss "List" operation?

}
},
"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.EventHub/namespaces/{namespaceName}/messagingplan": {
"get": {
Copy link
Contributor

Choose a reason for hiding this comment

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

I do not see a network payload example - please add "x-ms-examples" for this operation

}
],
"responses": {
"200": {
Copy link
Contributor

Choose a reason for hiding this comment

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

     "200": [](start = 0, length = 16)

you need to specify default error response schema as well.

@hovsepm hovsepm added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Apr 6, 2018
@hovsepm
Copy link
Contributor

hovsepm commented Apr 6, 2018

@ravbhatnagar Could you check if this operation was approved by ARM?

Copy link
Contributor

@hovsepm hovsepm left a comment

Choose a reason for hiding this comment

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

@v-Ajnava could you point to some documentation about this feature? How this will be used by external customers?

@hovsepm
Copy link
Contributor

hovsepm commented Apr 6, 2018

@v-Ajnava also "Regions_ListBySku" opertaion does not have a payload sample. Could you add it in your PR? Because of it we have Linter rule failures.

@azuresdkciprbot
Copy link

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

💡 Please review potentially introduced Error(s)/Warning(s): Analysis Report 💡

File: specification/eventhub/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 1
After the PR: Warning(s): 0 Error(s): 2

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

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

Labels

WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

Comments