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
Fixing deployment status response parsing #557
Conversation
@@ -13,7 +13,7 @@ | |||
<PackageReference Include="Newtonsoft.Json" Version="[11.0.2]" /> | |||
<PackageReference Include="System.Runtime.Handles" Version="4.3.0" /> | |||
<PackageReference Include="System.IO.FileSystem.Primitives" Version="4.3.0" /> | |||
<PackageReference Include="Mono.Cecil" Version="0.11.1" /> | |||
<PackageReference Include="Mono.Cecil" Version="0.11.3" /> |
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.
Unrelated, but had to update to address a build issue.
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.
Change looks good -- but could you note what changed in the response? It wasn't entirely clear...
@fabiocav - I am assuming you will cherry-pick to the v3.0 branch as well right? |
@vijayrkn yes. Wanted to go through the review here first and once settled/approved, cherry pick to 3.0. Will go ahead and do that now. |
Microsoft.NET.Sdk.Functions version 4.1.1 is live in nuget gallery now. |
Resolves #556
This change is in response to a change in the API payload that broke the assumption made in the original implementation. The actual change was the introduction of a new
build_summary
property that carried a JSON object instead of a simple string value, causing a deserialization exception in the updated code path.