-
Notifications
You must be signed in to change notification settings - Fork 4.1k
update latest VMAccessAgent version to 2.4 instead of 2.0 #12243
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
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.
update latest VMAccessAgent version to 2.4 instead of 2.0
|
@VeryEarly Thanks - but we need to modify this page https://docs.microsoft.com/en-us/powershell/module/azurerm.compute/set-azurermvmaccessextension?view=azurermps-6.13.0 too. |
Hi @axelgMS , AzureRM was not been supported, we won't release new version for it anymore. |
I get this - and I'm not asking for a change in the cmdlet. I'm asking for a documentation change in the sample using it. I'm still using Set-AzureRmVMAccessExtension from time to time, as well as some customers. and by the way, where is it written that set-azurermvmaccessextension is not supported? I don't see anything in https://docs.microsoft.com/en-us/powershell/module/azurerm.compute/set-azurermvmaccessextension?view=azurermps-6.13.0 |
Hi @axelgMS , "It's not supported" means we won't release new version for it, any fix made here won't be published. Thanks |
|
closing here - I opened update latest VMAccessAgent version to 2.4 instead of 2.0 #1452 in the MS Docs |
same as #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.
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