-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
[Hub Generated] Review request for Microsoft.Consumption to add version 2019-01-01 #5139
[Hub Generated] Review request for Microsoft.Consumption to add version 2019-01-01 #5139
Conversation
Automation for azure-sdk-for-jsThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-rubyThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaThe initial PR has been merged into your service PR: |
Can one of the admins verify this patch? |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Taking this PR as I was reviewing the original, which is getting abandoned. |
Doesnt look like any changes other than api version change. Signing off from ARM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one comment to update Java code generation in reamde.md file, rest looks good! Thanks for submitting a new PR with clearer commits.
@anuchandy could you help taking a look at the failure for Java generation? Java was missing from swagger to SDK configuration and as I added it, I'm seeing it failing. Thanks! |
@shbha I noticed Java SDK wasn't getting generated, I added the language to the readme.md configuration and it's now producing a failure, so would like to hear back from one of the Java SDK owners. After solving that failure, we should be good to merge this PR. |
@veronicagg - Delay merge or PR. Upon internal review of this PR there is a requirement to introduce additional changes. 1) define and use method.parameter scope and introduce a few new scopes for existing methods. Arm provided this review on a different PR ( for a different specification RP) and I would like to follow best practices here as well. I would really appreciate it if we could hold off on merge till these changes are made. |
@shbha sure, thanks for letting me know, I've edited the title to indicate this. In the meantime, we're investigating the Java SDK failure generation. Please keep me posted on progress, thanks! |
introduce scope (method) parameter for APIs that support numerous scopes (arm-team suggestion implemented)
The required changes have been made @veronicagg. Thank you |
...cation/consumption/resource-manager/Microsoft.Consumption/stable/2019-01-01/consumption.json
Outdated
Show resolved
Hide resolved
* Fixing Java code-generation * Removing duplicate directive from java section
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the updates.
If you are a MSFT employee you can view your work branch via this link.
Contribution checklist: