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

Add message regarding tenant level resources to ListByResourceGroup & ListBySubscriptions #2390

Merged
merged 1 commit into from
Jun 28, 2017

Conversation

sarangan12
Copy link
Member

Please review and approve Related to #2389

Copy link
Contributor

@vishrutshah vishrutshah left a comment

Choose a reason for hiding this comment

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

Left one question out of curiosity.

@@ -251,10 +251,10 @@ Modelers:
<value>For the tracked resource '{0}', the x-ms-pageable extension values must be same for list by resource group and subscriptions operations.</value>
</data>
<data name="TrackedResourceListByResourceGroupOperationMissing" xml:space="preserve">
<value>The tracked resource, '{0}', must have a list by resource group operation.</value>
<value>The tracked resource, '{0}', must have a list by resource group operation.(This rule does not apply for tenant level resources.)</value>
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we detect tenant level resource from the path of the operation to improve the logic of the rule?

Copy link
Member Author

Choose a reason for hiding this comment

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

Not as of now. This was decided in one of our earlier discussion

Copy link
Contributor

@dsgouda dsgouda left a comment

Choose a reason for hiding this comment

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

LGTM

@sarangan12 sarangan12 merged commit 8570d2c into Azure:master Jun 28, 2017
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.

5 participants