Update New-AzGalleryImageVersion.md example with correct value for StorageAccountType

[cocallaw]

Update the value passed to parameter -StorageAccountType from 'StandardSSD_LRS' to 'Standard_LRS' in two PowerShell examples

Description

The current documentation provides two examples where the value of 'StandardSSD_LRS' is provided for the parameter -StorageAccountType. This is not a proper value as defined in another section of this documentation and in the error message that is returned when the incorrect value is used. The possible correct values are Standard_LRS, Standard_ZRS and Premium_LRS

If the current incorrect value listed 'StandardSSD_LRS' is used, the cmdlet will fail with the following error message:

PS /home/corey> $storageAccountType = "StandardSSD_LRS"
PS /home/corey> 
PS /home/corey> New-AzGalleryImageVersion -ResourceGroupName $rgName -GalleryName $galleryName -GalleryImageDefinitionName $galleryImageDefinitionName -Name $galleryImageVersionName -Location $location -StorageAccountType $storageAccountType -SourceImageId $sourceImageId
New-AzGalleryImageVersion: The value 'StandardSSD_LRS' of parameter 'galleryImageVersion.properties.publishingProfile.storageAccountType' is not allowed. Allowed values are: Standard_LRS, Standard_ZRS, Premium_LRS.
ErrorCode: InvalidParameter
ErrorMessage: The value 'StandardSSD_LRS' of parameter 'galleryImageVersion.properties.publishingProfile.storageAccountType' is not allowed. Allowed values are: Standard_LRS, Standard_ZRS, Premium_LRS.
ErrorTarget: galleryImageVersion.properties.publishingProfile.storageAccountType
StatusCode: 400
ReasonPhrase: Bad Request

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

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

⚠️Help Example Check

⚠️PowerShell Core - Windows

Type	Cmdlet	Example	Line	RuleName	Description	Extent	Remediation
⚠️	New-AzGalleryImageVersion	11	6	Unassigned_Variable	New-AzGalleryImageVersion -SourceImageId $sourceImageId is a null-valued parameter value.	-SourceImageId	Assign value for $sourceImageId.
⚠️	New-AzGalleryImageVersion	12	7	Unassigned_Variable	New-AzGalleryImageVersion -SourceImageId $sourceImageId is a null-valued parameter value.	-SourceImageId	Assign value for $sourceImageId.

⚠️Windows PowerShell - Windows

Type	Cmdlet	Example	Line	RuleName	Description	Extent	Remediation
⚠️	New-AzGalleryImageVersion	11	6	Unassigned_Variable	New-AzGalleryImageVersion -SourceImageId $sourceImageId is a null-valued parameter value.	-SourceImageId	Assign value for $sourceImageId.
⚠️	New-AzGalleryImageVersion	12	7	Unassigned_Variable	New-AzGalleryImageVersion -SourceImageId $sourceImageId is a null-valued parameter value.	-SourceImageId	Assign value for $sourceImageId.

️✔️Help File Existence Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

[Nickcandy]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Nickcandy]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).