-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[Feature]: Add TimeCreated property to Vmss VM model #22774
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @TravisCragg-MSFT, @sandeepraichura. |
1 similar comment
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @TravisCragg-MSFT, @sandeepraichura. |
@bmuller4 Thank you for your feedback! we are looking into this request now. |
@bmuller4, the TimeCreated property exists for all VMs, VM Scale Sets and VM instances in VMSS starting with API version 2021-11-01. Below is an example of this for a VMSS instance shown in the portal. Could you let us know if you are looking for something different or did you maybe not know the time created property already existed? |
@Drewm3 You're absolutely correct that is exists foundationally as an object property for VMs, VMSS and VMSS instances but because it is missing from the PSVirtualMachineScaleSetVM Class this property is not accessible via the Get-AzVmssVM cmdlet which is what this FR is about. |
@bmuller4 we have added this item to our backlog. Will update once this feature is picked up, thanks! |
fix has been merged. closing this issue |
Description of the new feature
The feature request #19478 was submitted to add the timeCreated property for VMs and VM scale sets. This feature request is to also add it to VM scale set VMs, specifically the PSVirtualMachineScaleSetVM Class so that the property can be retrieved via Get-AzVmssVM.
Without this property it's not possible to determine when a scale set VM was created using the Azure PowerShell module.
Proposed implementation details (optional)
No response
The text was updated successfully, but these errors were encountered: