-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
SDK changes for swagger update to support AutomaticRepairsPolicy for Virtual Machine Scale Sets #8141
Conversation
sdk/compute/Microsoft.Azure.Management.Compute/src/Generated/Models/OSProfile.cs
Show resolved
Hide resolved
sdk/compute/Microsoft.Azure.Management.Compute/src/Generated/Models/ScaleInPolicy.cs
Show resolved
Hide resolved
sdk/compute/Microsoft.Azure.Management.Compute/src/Generated/Models/VirtualMachineScaleSet.cs
Show resolved
Hide resolved
[assembly: AssemblyVersion("29.1.0.0")] | ||
[assembly: AssemblyFileVersion("29.0.0.0")] | ||
[assembly: AssemblyVersion("29.2.0.0")] | ||
[assembly: AssemblyFileVersion("29.2.0.0")] |
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 don't have to update AssemblyFileVersion for minor version update. Leave it to 29.0.0.0
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.
Fixed.
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.
@hyonholee @hapandar That is not correct. AssemblyFileVersion
needs to be updated for every release, AssemblyVersion
only when introducing a breaking change (aka a major version update).
So my suggestion is:
[assembly: AssemblyVersion("29.1.0.0")]
[assembly: AssemblyFileVersion("29.2.0.0")]
Read about it in our process document: https://github.com/Azure/adx-documentation-pr/blob/master/engineering/adx_netsdk_process.md#signing-and-publishing-nuget-packges
An article explaining this: https://support.microsoft.com/en-us/help/556041
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.
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.
Fixed
sdk/compute/Microsoft.Azure.Management.Compute/src/Microsoft.Azure.Management.Compute.csproj
Outdated
Show resolved
Hide resolved
LGTM |
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.
Please see my comment in the above conversation. Thanks
sdk/compute/Microsoft.Azure.Management.Compute/src/Microsoft.Azure.Management.Compute.csproj
Show resolved
Hide resolved
/azp run net - mgmt - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
This SDK PR includes the below Swagger updates:
Azure/azure-rest-api-specs#7484
Azure/azure-rest-api-specs#7513
Azure/azure-rest-api-specs#7355
Azure/azure-rest-api-specs#7034
Resolved. Including the additional changes
Note: when I ran code gen tool, there were other changes (which were not part of my swagger changes) that were generated as well. Is the best practice to revert these changes?
Please let me know and I can plan to revert those changes manually. For example, the ScaleInPolicy is not part of my changes and is not covered as part of the tests I have written.