Publish a resource with version 1.0.0.0. Publish-PSResource will succeed, but Find-PSResource with -Version "1.0", "1.0.0", "1.0.0.0" will all fail. This is because PSResourceGet code converts the user inputted version to a Normalized Version, so "1.0" becomes "1.0.0" or "1.0.0.0" becomes "1.0.0" and ACR requires the exact tag to find the package, so anything aside from "1.0.0.0" will fail and give a Package Not Found error.
This occurs if the version has 4 digits and ends with 0, or if the version has 2 digits and ends with 0.
Expected behavior
Given that a package myPkg with version "1.0.0.0" is published, all the following should work
Find-PSResource -Name "myPkg" -Version "1.0"
Find-PSResource -Name "myPkg" -Version "1.0.0"
Find-PSResource -Name "myPkg" -Version "1.0.0.0"
Actual behavior
Given that a package myPkg with version "1.0.0.0" is published, the following do not work and package is not found:
Find-PSResource -Name "myPkg" -Version "1.0"
Find-PSResource -Name "myPkg" -Version "1.0.0"
Find-PSResource -Name "myPkg" -Version "1.0.0.0"
Prerequisites
Steps to reproduce
Publish a resource with version 1.0.0.0. Publish-PSResource will succeed, but Find-PSResource with -Version "1.0", "1.0.0", "1.0.0.0" will all fail. This is because PSResourceGet code converts the user inputted version to a Normalized Version, so "1.0" becomes "1.0.0" or "1.0.0.0" becomes "1.0.0" and ACR requires the exact tag to find the package, so anything aside from "1.0.0.0" will fail and give a Package Not Found error.
This occurs if the version has 4 digits and ends with 0, or if the version has 2 digits and ends with 0.
Expected behavior
Actual behavior
Error details
No response
Environment data
Visuals
No response