-
Notifications
You must be signed in to change notification settings - Fork 4k
[Compute] Bug fix in Invoke-AzVMPatchAssessment #25714
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -29,7 +29,7 @@ public class PSVirtualMachinePatchAssessmentResult | |
public int? CriticalAndSecurityPatchCount { get; set; } | ||
public int? OtherPatchCount { get; set; } | ||
public DateTime? StartDateTime { get; set; } | ||
public IList<VirtualMachineSoftwarePatchProperties> Patches { get; set; } | ||
public IList<VirtualMachineSoftwarePatchProperties> AvailablePatches { get; private set; } | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So the issue was that the PS object made up a nonexistent Patches property instead of the AvailablePatches property which actually exists on the VirtualMachineAssessPatchesResult.cs object? |
||
public ApiError Error { get; set; } | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please write a test for this as the initial functionality seems to have never been tested as this issue would have been caught back then. |
||
} | ||
} |
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.
you need to add a breaking change suppression to this file:
tools/StaticAnalysis/Exceptions/Az.Compute/BreakingChangeIssues.csv
and add a description to this PR describing why you need to do this and it is not really a breaking change.