[Hub Generated] Review request for Microsoft.Consumption to add version stable/2019-05-01#6620
Conversation
…-01-01 to version 2019-05-01
Updated scope for Usage detail list
usage detail
syntax error fix
syntax fix
fixing syntax error
added scope parameter
scope added
added scope
added scope
added scope
added scope
added scope
added scope
added scope
json correction
syntax correction
added reservationRecommendation, RI Usage Summary and RI Usage details
syntax correction
…on/stable/2019-05-01/examples/ReservationSummariesDaily.json Co-Authored-By: Nick Schonning <nschonni@gmail.com>
…tps://github.com/santoshsinha100/azure-rest-api-specs into dev-consumption-Microsoft.Consumption-2019-05-01
|
Hi Nick, Can you mark this item complete. I already addressed all your suggestions. We need this to roll out ASAP. Thanks & Regards |
|
Sorry, I'm not an MS employee, but I think there is instructions over here if you need to escalate https://armwiki.azurewebsites.net/rp_onboarding/ResourceProviderOnboardingAPIRevieworkflow.html |
|
Can some one please approve this PR. This is active since last 4 to 5 days. |
|
We have preview version for usage details already merged in |
nit - should be camelCase Refers to: specification/consumption/resource-manager/Microsoft.Consumption/stable/2019-05-01/consumption.json:968 in d04e302. [](commit_id = d04e302, deletion_comment = False) |
This is potentially an SDK breaking change. (When users update the current SDK to one generated from this Swagger, their code won't compile if they are referencing properties that got removed.) What's the plan to deal with that? Refers to: specification/consumption/resource-manager/Microsoft.Consumption/stable/2019-05-01/consumption.json:1269 in 71e2dcb. [](commit_id = 71e2dcb, deletion_comment = True) |
|
Can some one do this review on priority. Its waiting for an approval |
I'm confused by this. Normally a person from the SDK team is assigned to a PR like this and they finish the review from the SDK side once ARM (me this week) signs off. I'll send an email to a contact I know internally (I don't know her GitHub name to just @ mention here.) |
|
If you reach out to me directly via Teams (alias is same as my github name), I can add you to the mail thread. |
yungezz
left a comment
There was a problem hiding this comment.
looks good, some minor issue in samples. @santoshsinha100 could you pls resolve conflict? then I'll go to approve and merge the PR.
| ], | ||
| "excludedSubscriptions": [], | ||
| "usageStart": "2019-05-01T00:00:00.0000000Z", | ||
| "usageEnd": "2018-10-31T00:00:00.0000000Z", |
There was a problem hiding this comment.
usageStart is later than usageEnd
There was a problem hiding this comment.
Hi I am unable to resolve the conflict in readme.md file. UI doesn't allow me to resolve. Looking at the conflict, I will go with "### Tag: package-2019-05" not the preview one. Will it be possible to get this resolved at your end .
| "api-version": "2019-05-01", | ||
| "billingAccountId": "1234", | ||
| "departmentId": "42425", | ||
| "scope": "providers/Microsoft.Billing/BillingAccounts/1234", |
In Testing, Please Ignore[Logs] (Generated from 052f9db, Iteration 1)
|
|
@santoshsinha100 pls look at the resolved readme.md file. pls update the tag |
yungezz
left a comment
There was a problem hiding this comment.
pls review change in readme.md for conflict resolving, and update tag name per need.
If you are a MSFT employee you can view your work branch via this link.
Contribution checklist: