Skip to content

Conversation

@allencal
Copy link
Contributor

@allencal allencal commented Oct 25, 2017

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

…raffic Manager.

[Traffic Manager] Adding new RealtimeUserMetrics preview feature to Traffic Manager.
…ure.

[Traffic Manager] Adding new Realtime User Metrics (RUM) preview feature.
…ure.

[Traffic Manager] Adding new Realtime User Metrics (RUM) preview feature.
…ure.

[Traffic Manager] Adding new Realtime User Metrics (RUM) preview feature.
…ure.

[Traffic Manager] Adding new Realtime User Metrics (RUM) preview feature.
…ure.

[Traffic Manager] Adding new Realtime User Metrics (RUM) preview feature.
…ure.

[Traffic Manager] Adding new Realtime User Metrics (RUM) preview feature.
…ure.

[Traffic Manager] Adding new Realtime User Metrics (RUM) preview feature.
Changes for real user metrics
# Conflicts:
#	specification/trafficmanager/resource-manager/Microsoft.Network/2017-05-01/trafficmanager.json
This reverts commit b703b5e.
@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/trafficmanager/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.

@lmazuel lmazuel self-requested a review October 26, 2017 16:07
"properties": {
"id": {
"type" : "string",
"description": "Fully qualified resource Id for the resource. Ex - /providers/Microsoft.Network/trafficManagerUserMetricsKeys/default"
Copy link
Member

Choose a reason for hiding this comment

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

It seems you removed "default" evrywhere else, is the description still accurate?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You're right, I think I should change this here. The "/default" is still returned in this description, though it shouldn't be; the call with "/default" on the end fails. I'll remove it here, and also in the API operation.

"$ref": "#/definitions/TrafficManagerUserMetricsKeyModel"
}
},
"204": {
Copy link
Member

Choose a reason for hiding this comment

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

Does this mean that 204 is impossible, or you want now a 204 to raise an exception?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The "Get" operation never returns a 204. If the subscription has no RUM key, it returns a 200 and the body returns a blank key ("key": "")

@lmazuel lmazuel changed the title Real User Metrics (RUM) fixes [TrafficManager] Real User Metrics (RUM) fixes Oct 26, 2017
…om resource ID and operation ID

[TrafficManager] Real User Metrics (RUM) fixes II - remove default from resource ID and operation ID
@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/trafficmanager/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.

Copy link
Member

@lmazuel lmazuel left a comment

Choose a reason for hiding this comment

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

LGTM. Tell me if you sign-off or if you have more to add.

@allencal
Copy link
Contributor Author

allencal commented Nov 1, 2017

I do not have more to add. I'm not authorized to merge this pull request. What happens next?

@lmazuel
Copy link
Member

lmazuel commented Nov 2, 2017

@allencal Next is I merge :)
If your question is "next-next" like SDK/CLI, please send me an email (my github alias is my MS alias)

@lmazuel lmazuel merged commit 342d0f9 into Azure:current Nov 2, 2017
@AutorestCI
Copy link

No modification for AutorestCI/azure-sdk-for-node

@AutorestCI
Copy link

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants