PowerShell Cmdlets for ComputeFleet

[cicichenmicrosoft]

Description

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.)

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

• [x] 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[bot]]

️✔️Az.Accounts

>

>

️✔️Build

> >>

>>

️✔️PowerShell Core - Windows

>> >> >>

>

⚠️Az.ComputeFleet

>

>

️✔️Build

> >>

>>

️✔️PowerShell Core - Windows

>> >> >>

>

>

>

️✔️Breaking Change Check

> >>

>>

️✔️PowerShell Core - Windows

>> >> >>

>

>

>

⚠️Signature Check

> >>

>>

⚠️PowerShell Core - Windows

>> >>|Type|Cmdlet|Description|Remediation| >>|---|---|---|---| >>|⚠️|Get-AzComputeFleet|Get-AzComputeFleet 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-AzComputeFleet|Get-AzComputeFleet 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-AzComputeFleetVMSS|Get-AzComputeFleetVMSS 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-AzComputeFleetVMSS|Get-AzComputeFleetVMSS 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| >>|---|---|---|---|---|---|---|---| >>|⚠️|Get-AzComputeFleet|4|2|Mismatched_Parameter_Value_Type|Get-AzComputeFleet -InputObject $fleet is not an expected parameter value type.|-InputObject|Use correct parameter value type. Expected Type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IComputeFleetIdentity. Now the type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IFleet.(Command).| >>|⚠️|New-AzComputeFleet|2|2|Mismatched_Parameter_Value_Type|New-AzComputeFleet -InputObject $fleet is not an expected parameter value type.|-InputObject|Use correct parameter value type. Expected Type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IComputeFleetIdentity. Now the type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IFleet.(Command).| >>|⚠️|Remove-AzComputeFleet|2|2|Mismatched_Parameter_Value_Type|Remove-AzComputeFleet -InputObject $fleet is not an expected parameter value type.|-InputObject|Use correct parameter value type. Expected Type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IComputeFleetIdentity. Now the type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IFleet.(Command).| >>|⚠️|Update-AzComputeFleet|1|1|Unassigned_Variable|Get-AzComputeFleet -SubscriptionId $env.SubscriptionId is a null-valued parameter value.|-SubscriptionId|Assign value for $env.SubscriptionId.| >>|⚠️|Update-AzComputeFleet|2|5|Mismatched_Parameter_Value_Type|Update-AzComputeFleet -InputObject $fleet is not an expected parameter value type.|-InputObject|Use correct parameter value type. Expected Type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IComputeFleetIdentity. Now the type is Microsoft.Azure.PowerShell.Cmdlets.ComputeFleet.Models.IFleet.(Command).| >> >>

>

>

>

️✔️Help File Existence Check

> >>

>>

️✔️PowerShell Core - Windows

>> >> >>

>

>

>

⚠️File Change Check

> >>

>>

⚠️PowerShell Core - Windows

>> >>|Type|Cmdlet|Description|Remediation| >>|---|---|---|---| >>|⚠️||AssemblyInfo.cs will be updated automatically. Please do not update it manually.|Revert AssemblyInfo.cs to its last version.| >>|⚠️||It is required to update ChangeLog.md if you want to release a new version for Az.ComputeFleet.|Add a changelog record under Upcoming Release section with past tense.| >> >>

>

>

>

️✔️UX Metadata Check

> >>

>>

️✔️PowerShell Core - Windows

>> >> >>

>

>

>

️✔️Test

> >>

>>

️✔️PowerShell Core - Linux

>> >> >>

>>

>>

️✔️PowerShell Core - MacOS

>> >> >>

>>

>>

️✔️PowerShell Core - Windows

>> >> >>

>

[VeryEarly]

/azp run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 3 pipeline(s).

[VeryEarly]

there is a fake password used in test cases: "testPassword01%", please search the occurrence in all *.recording.json and replace them with [Sanitized]

[VeryEarly]

/azp run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 3 pipeline(s).