Example was missing Update-AzVM cmdlet#12205
Example was missing Update-AzVM cmdlet#12205VeryEarly merged 3 commits intoAzure:masterfrom michawets:patch-3
Conversation
When running the example, the diagnostics settings were not applied to the VM, only to the variable stored in the Powershell windows at that moment. No real update was done on the VM. For the diagnostics to be applied, the cmdlet Update-AzVM still needs to be executed
|
looks like the updated vm need to be passed to Update-AzVM, please check my commit and confirm. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Hi @VeryEarly , there are multiple ways to do it 😊. I double checked my commit, and that will work. I didn't want to change to much on the example, and keep the $VM variable as a single variable So the $updatedVM variable is actually not needed 😊 |
You're right,I'll revert my commit. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
* Example was missing Update-AzVM cmdlet When running the example, the diagnostics settings were not applied to the VM, only to the variable stored in the Powershell windows at that moment. No real update was done on the VM. For the diagnostics to be applied, the cmdlet Update-AzVM still needs to be executed * Update Set-AzVMBootDiagnostic.md * Update Set-AzVMBootDiagnostic.md Co-authored-by: Yabo Hu <yabhu@microsoft.com>
When running the example, the diagnostics settings were not applied to the VM, only to the variable stored in the Powershell windows at that moment. No real update was done on the VM.
For the diagnostics to be applied, the cmdlet Update-AzVM still needs to be executed
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