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

Fix the examples in Consumption #5625

Closed
anuchandy opened this issue Apr 12, 2019 · 4 comments
Closed

Fix the examples in Consumption #5625

anuchandy opened this issue Apr 12, 2019 · 4 comments
Labels
question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@anuchandy
Copy link
Member

There are existing model validation errors for Consumption. Refer https://travis-ci.org/Azure/azure-rest-api-specs/jobs/518056993

@bgsky
Copy link
Contributor

bgsky commented Apr 12, 2019

Thanks for creating an issue to help track progress on scope validations. We will propose a new preview version to address scope validations soon.

@akning-ms akning-ms added the Service Attention Workflow: This issue is responsible by Azure service team. label May 27, 2020
@ghost
Copy link

ghost commented May 27, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ms-premp.

@ms-premp
Copy link
Contributor

This should already be resolved.

@ramaganesan-rg ramaganesan-rg added the question The issue doesn't require a change to the product in order to be resolved. Most issues start as that label Jun 29, 2020
@ramaganesan-rg
Copy link
Member

Resolving as per Prem's comments. thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

5 participants