-
Notifications
You must be signed in to change notification settings - Fork 164
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
Preview apiVersion in generated ARM templates - do we need to filter versions? #834
Comments
Thank you for reporting! It indeed looks like something's changed with the output from Get-AzResourceProvider cmdlet. We'll investigate. |
I've done some digging with the product group and it turns out this behavior has been around since day one 😄. |
Thanks for investigating! Seems like a really good approach. Personally, I was kind of confused as to why this was default behavior where the |
That's a reasonable guess 😄. But here's an interesting bit: many Az.PowerShell cmdlets, include the |
Describe the bug
AzOps versions 2.3.0 and 2.3.1
Since a day or two the 'pull' pipeline decided to update all apiVersions in all files more or less, some of the them with preview status. Something must have changed with regards to the output from
Get-AzResourceProvider -ListAvailable
?Do we need to filter or sort the returned api versions perhaps?
Any other idea would be most welcome?
I found #422 and related #425 from two years back.
Below is an example for an ordinary resource group and what we see.
Steps to reproduce
Connect-AzAccount ...
(Get-AzResourceProvider -ListAvailable).ResourceTypes | Where-Object { $_.ResourceTypeName -eq "resourceGroups" } | Select-Object -ExpandProperty ApiVersions
to partly mimic the code at
AzOps/src/functions/Initialize-AzOpsEnvironment.ps1
Line 106 in d34b87f
and
AzOps/src/internal/functions/ConvertTo-AzOpsState.ps1
Line 225 in d34b87f
Screenshots
The text was updated successfully, but these errors were encountered: