Uh oh!
There was an error while loading. Please reload this page.
Add 'innererror' property bag to CloudError contract - #338
Add 'innererror' property bag to CloudError contract#338Ilia Demianenko (ilidemi) wants to merge 4 commits into
Conversation
Jianghao Lu (jianghaolu)
left a comment
There was a problem hiding this comment.
Thanks for contributing! Please take a look at the comment.
| /** | ||
| * The inner error. | ||
| */ | ||
| private ObjectNode innererror; |
There was a problem hiding this comment.
What's the format of the innerError? Will it be a HashMap? (judging on your test)
Also please camel case the variables and methods.
There was a problem hiding this comment.
It will be an arbitrary JSON struct with an object at the top level. Inside could be multiple levels of nesting, arrays and numbers.
Ilia Demianenko (ilidemi)
commented
Feb 16, 2018
Looks like all of the issues have been addressed. Is there anything else that needs to be changed? |
Anu Thomas (anuchandy)
commented
Feb 19, 2018
demyanenko based on the discussion with .net runtime team, our understanding is - shape of innerError is not yet finialized with ARM team. \cc Abhijeet (@shahabhijeet) |
The data contract for ARM errors includes
innererrorfield which is a property bag with unspecified contents as per OData 4.0 spec. This field wasn't used by ARM up until now, but recently there was a change related to Azure Policy that makes heavy use of this property bag. It is already deployed in all regions and consumed by Azure Portal, so now would be a good time to support it in SDKs as well.The new errors are generated by the ARM Frontdoor itself, so CloudError seems like the most appropriate contract to include it.