Versioning enhancements + fixes

[mentat9]

Description

• Complete support for getting and assigning versioned policy definitions and sets
• Fix for serialization issue with empty arrays in PolicyParameterObject (reported by Walgreens)
• Fix for GH issue: Get-AzPolicyDefinition : A parameter cannot be found that matches parameter name 'Depth'. #24971 - Get-AzPolicyDefinition : A parameter cannot be found that matches parameter name 'Depth'.
• Fixes GI issue: Unexpected error in Get-AzPolicySetDefinition 'A parameter cannot be found that matches parameter name 'Name'. #25334 - Unexpected error in Get-AzPolicySetDefinition 'A parameter cannot be found that matches parameter name 'Name'.
• Fix for IcM: https://portal.microsofticm.com/imp/v5/incidents/details/510594116/summary - Get-AzPolicyExemption requests unnecessary parameter for Get-AzPolicyExemption in v12
• Fix for -Scope parameter handling at resource instance level
• Fix for IcM: https://portal.microsofticm.com/imp/v5/incidents/details/515228129/summary - Policy import - Issue with OP (requires serialization of null values)
• Fix for handling string ID value of -PolicyDefinition parameter to New-AzPolicyAssignment
• Fix for GH issue: Set-AzPolicyAssignment Command Loses Description and Display Name #25362 - Set-AzPolicyAssignment Command Loses Description and Display Name
• Fix properties (IAny) dropped from serialization in versioned types
• Add explicit -DefinitionVersion parameter to New-AzPolicyAssignment
• Add -Scope examples for New-AzPolicyExemption
• Add -Tag 'LiveOnly' to tests that create the two largest recording files

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • For SDK-based development mode, update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • For autorest-based development mode, include the changelog in the PR description.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

️✔️Az.Accounts

️✔️Build

️✔️PowerShell Core - Windows

⚠️Az.Resources

️✔️Build

️✔️PowerShell Core - Windows

️✔️Breaking Change Check

️✔️PowerShell Core - Windows

⚠️Signature Check

⚠️PowerShell Core - Windows

Type	Cmdlet	Description	Remediation
⚠️	Get-AzADGroupOwner	Get-AzADGroupOwner Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzADGroupOwner	Get-AzADGroupOwner changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️	Get-AzADServicePrincipalAppRoleAssignment	Get-AzADServicePrincipalAppRoleAssignment Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzADServicePrincipalAppRoleAssignment	Get-AzADServicePrincipalAppRoleAssignment changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️	Get-AzPolicyAssignment	Get-AzPolicyAssignment Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzPolicyAssignment	Get-AzPolicyAssignment changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️	Get-AzPolicyDefinition	Get-AzPolicyDefinition Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzPolicyDefinition	Get-AzPolicyDefinition changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️	Get-AzPolicyExemption	Get-AzPolicyExemption Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzPolicyExemption	Get-AzPolicyExemption changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️	Get-AzPolicySetDefinition	Get-AzPolicySetDefinition Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzPolicySetDefinition	Get-AzPolicySetDefinition changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.

⚠️Help Example Check

⚠️PowerShell Core - Windows

Type	Cmdlet	Example	Line	RuleName	Description	Extent	Remediation
⚠️	New-AzPolicyExemption	3	3	Mismatched_Parameter_Value_Type	New-AzPolicyExemption -PolicyAssignment $Assignment is not an expected parameter value type.	-PolicyAssignment	Use correct parameter value type. Expected Type is psobject. Now the type is Microsoft.Azure.PowerShell.Cmdlets.Policy.Models.IPolicyAssignment.(Command).
⚠️	New-AzPolicyExemption	4	3	Mismatched_Parameter_Value_Type	New-AzPolicyExemption -PolicyAssignment $Assignment is not an expected parameter value type.	-PolicyAssignment	Use correct parameter value type. Expected Type is psobject. Now the type is Microsoft.Azure.PowerShell.Cmdlets.Policy.Models.IPolicyAssignment.(Command).
⚠️	New-AzPolicyExemption	4	3	Unassigned_Variable	New-AzPolicyExemption -Scope $SpecialVM.Id is a null-valued parameter value.	-Scope	Assign value for $SpecialVM.Id.

️✔️Help File Existence Check

️✔️PowerShell Core - Windows

⚠️File Change Check

⚠️PowerShell Core - Windows

Type	Cmdlet	Description	Remediation
⚠️		It is required to update ChangeLog.md if you want to release a new version for Az.Resources.	Add a changelog record under Upcoming Release section with past tense.

️✔️UX Metadata Check

️✔️PowerShell Core - Windows

⚠️Test

⚠️ - Linux

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	0.00 %	Test coverage for the module cannot be lower than 50%.

⚠️ - MacOS

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	0.00%	Test coverage for the module cannot be lower than 50%.

⚠️PowerShell Core - Windows

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	0.00%	Test coverage for the module cannot be lower than 50%.