EC2 Filter Change in v5.0.67

[aspersram]

I have noticed that if I create a ec2 filter in v5.0.67, the object has changed: $filter=new-object amazon.ec2.model.filter
v4:
{
"Name": null,
"Values": [

]
}

v5:
{
"Name": null,
"Values": null,
"Value": null
}
Is v5 going to be the standard going forward?
And if so, are there any other filters that will have changed?

[afroz429]

I believe this is not a V4/V5 difference, this is an AWSPowerShell vs AWS.Tools.EC2 difference. For backwards compatibility reasons, an alias is being added for Values property. so the Value and Values property are the same. As can be seen from the below output, Value is an alias that points to Values in AWSPowerShell module. This alias is not being added to AWS.Tools.EC2. I have added link to relevant code. As for what other filters the alias exists, please refer to the file. I would recommend using AWS.Tools.EC2 module instead of AWSPowerShell. Please reach out if you have any more questions.

Get-Module AWSPowerShell| select Version

Version
-------
5.0.60


$filter=new-object amazon.ec2.model.filter
$filter | get-member

   TypeName: Amazon.EC2.Model.Filter

Name        MemberType    Definition
----        ----------    ----------
Value       AliasProperty Value = Values
Equals      Method        bool Equals(System.Object obj)
GetHashCode Method        int GetHashCode()
GetType     Method        type GetType()
ToString    Method        string ToString()
Name        Property      string Name {get;set;}
Values      Property      System.Collections.Generic.List[string] Values {get;set;}

See https://github.com/aws/aws-tools-for-powershell/blob/main/modules/AWSPowerShell/AWSPowerShell.TypeExtensions.ps1xml#L448-L455