-
Notifications
You must be signed in to change notification settings - Fork 4.1k
update latest VMAccessAgent version to 2.4 instead of 2.0 #10755
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
Conversation
version 2.0 is pretty old and users should use 2.4 instead so I'm modifying the sample here to ensure they're using latest version.
|
@axelgMS Please update src/Compute/Compute/ChangeLog.md A snippet outlining the changes made in the PR is added under the ### Upcoming Release header in the module's ChangeLog.md file |
|
@dingmeng-xue thanks, I modified changelog.md Note that there was no ### upcoming release header - so I created one at the top of the changelog.md file |
f0c9064 to
e742a1e
Compare
e742a1e to
a70c823
Compare
|
Test failed due to a case in data lake store. Will merge anyway. |
|
also related to 12687 |
update latest VMAccessAgent version to 2.4 instead of 2.0
same as #10755 version 2.0 is pretty old and users should use 2.4 instead so I'm modifying the sample here to ensure they're using latest version.
same as Azure/azure-powershell#10755 - but for **_Set-AzureRmVMAccessExtension_** version 2.0 is pretty old and users should use 2.4 instead so I'm modifying the sample here to ensure they're using latest version.
IcM 163809520
version 2.0 is pretty old and users should use 2.4 instead
so I'm modifying the sample here to ensure they're using latest version.
Description
Checklist
CONTRIBUTING.mdChangeLog.mdfile(s) has been updated:ChangeLog.mdfile can be found atsrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md## Upcoming Releaseheader -- no new version header should be added